Vincent Rogier

Hi, A resultset lifetime is bound to its statement parent object which lifetime is also bound to its parent connection object. OCILIB C++ object are used as value object but...

Current c++ Api objects keep tracks of the C API handles, not C++ objects. I agree that maintaining a reference to resultset should keep the connection object in memory. I...

GetCount() returns the number of fetched rows. It is updated after each fetch operation. There is no way to get row count in advance except using scrollable cursors

Closing the issue as not a bug and and more related to API usage.

Hi, To be honest, I have never tried this workflow (get sql identifier on scrollable cursors). I will investigate that asap. Regards, Vincent

Hi, I did have a look at it. Every time a statement is executed and if the OCI client supports it, OCILIB retrieves the SQL ID of the just executed...

Created v4.7.7 branch with the optimization that computes the SQL ID only once. I am still questioning the OCI client behavior (the issue could be in OCILIB usage of the...

> @vrogier an OCI testcase would help us. @cjbj Here it is :) When executing this pure OCI test case with exec_mode = OCI_DEFAULT, SQL ID can be retrieved after...

Hi, Thanks for reporting this issue. it will be fixed for v4.7.7 release. Regards, Vincent

Hi, This will be added to OCILIB in version V4.8.0 (as this will result in a new API function) soon. Regards, Vincent