On Wed, Mar 13, 2002 at 12:52:30AM -0800, Daniel Ceregatti wrote :
> Well, this leaves one question: Should I even bother passing the sql
> statement? Presumably, the developer will have access to the sql
> statement in the script/class already, so the offset _should_ suffice.
> This is actual
Well, this leaves one question: Should I even bother passing the sql
statement? Presumably, the developer will have access to the sql
statement in the script/class already, so the offset _should_ suffice.
This is actually what I originally implemented, but I thought I'd go the
extra kilometer
Agree! You could provide afunction for your html output and
make it an examle in the documentations - then everyone
knows how to make nice error messages and those needing
correct ones can do it too.
Besides that i often needed some time to see the asterix in
long statements (multiple subselects)
Hey,
I'm not quite sure it's correct for the error message to print HTML itself.
It's probably more correct to do this from user land.
In any case, you should not be using malloc()/free() but emalloc()/efree().
If the request gets interrupted the memory will be freed if you're using
emalloc().
Ahh. very kewl patch Dan.
Walt
On Tue, 2002-03-12 at 12:48, Daniel Ceregatti wrote:
> Hi,
>
> I wrote a small patch to oci8.c's OCIError function which places the
> following tag:
>
>
>
> just before an error in a sql statement and adds the modified statement
> text into a new elem
