I was about to upgrade our installation when I noticed this in the changelog. Tim Bunce <[EMAIL PROTECTED]> writes: > Changes in DBD::Oracle 1.09 27th August 2001 > > Changed behaviour when OCIStmtExecute() returns OCI_SUCCESS_WITH_INFO: > used to be treated as OCI_SUCCESS, now also sets $DBI::err/$DBI::errstr > and will therefore trigger RaiseError/PrintError if they are set. We ran into this problem once before when we first upgraded to Oracle 8.1.6. At that time executing random statements would cause an error if this was returned. We fixed it by upgrading DBD::Oracle to a version that ignored OCI_SUCCSES_WITH_INFO. Is this reverting to the previous behaviour? Do we have to now go through all our SQL statements looking for anything that could return this and catch errors? Is there a simply way to recognize this condition? We have a wrapper function where we could check for this condition and hide the error from the rest of the application. -- greg
