Personally I think if you spent the dollars on a product and it doesn't do what it is supposed to do then you
ought to let whomever you bought it from know.
You should also make whatever *temporary workarounds* you need to get through the day, and perhaps
you can send the vendor the temporary workaround (or a description of it) so they completely understand
that you understand the problem.
First rule is always get through the day though - so if perl can bandage a problem until Oracle fixes it properly
then perl (once again) is the right tool in the right place at the right time.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.