Re: OCI - How to find which column caused a bind error

Hi James:

You may use printf() in the OCI program to print out which column caused the error.

If you print out all variable binded, you may see there is some string is not in good order. That is they are not ended with proper '\0'.

Best regards,

News Postings (newspost_at_sandman.co.uk) wrote:
: With deferred mode linking, obndrv/n/a do not return errors such as
: invalid characters in numeric fields etc. These errors are only
: returned on a subsequent oexec or similar call.
 

: Is it possible to find out, after the oexec, which column actually
: caused the error?
 

: obndra, with its array of column-level error codes, doesn't seem to
: help - these just don't seem to be set for bind-type conversion errors
: (presumably they are used for select-type errors). Neither does the
: parse error offset in the cda help - by the time a bind error happens
: it is just set to the end of the statement.
Received on Sun Apr 13 1997 - 00:00:00 CEST