Replies: 1 comment
-
First finding on my side, we raise an exception when the error handler is called ... then the OCI_Error flag 'active' is not reset to the value FALSE ... WIP |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Helo
I migrated code from OCILIB 3.6 to 4.7.4 and 4.7.6
It is a legacy code the we maintain, with error handling based only the error handler, and we received exception as soon as the database connexion was down.
But now, with the new version, in certain circumstances I don't get a call to the error handler when the DB is down ... I noticed that our legacy code is not using the flag returned by OCI_Execute ...
I need to understand better the good strategy for error handling to fix our code regarding this issue
A note, when I initialise in mixed mode : OCI_ENV_DEFAULT | OCI_ENV_CONTEXT ... I would expect that in case of return false from OCI_Execute, I would be able to get information with OCI_GetLastError but it seems that it does not give the information expected ... maybe I am wrong in my use of the flag ?
Thanx in advance for any explanations or clues
Beta Was this translation helpful? Give feedback.
All reactions