Session level auto-commit

[drewbob]

Hello!

I'm relatively new to oracle, so i hope I use the correct terminology. Please let me know if my question doesn't make sense!
I'm trying to figure out how to turn off the session level auto-commit feature in my oracle oci.

I'm working in a linux environment, using c++. The problem I'm having is this:

when the connection to a database is severed (because the db object goes out of scope) the data written to any tables in that db is automatically committed, even if commit is not explicitly called.

Notice that this is different from transaction-level auto-commit. We are manually committing at the transaction level, that works fine. The problem is that data is being committed implicitly by the oci (i believe).

First Solution Idea: My first response was to call Rollback in the destructor to my oci. The problem with this is it only solves the problem when the program runs to completion. If, say, an impatient developer enters "ctrl+c" in the middle of a run, and the objects are not destructed properly, my problem will not be solved.

Thanks for your help,

Andrew

[drewbob]

I've been reading through the OCI manual, and it looks like the reason we autocommit is because we call: OCISessionEnd() in our destructor. This function calls commit implicitly. The documentation is here:
http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a96584/oci15r14.htm#556681

It doesn't mention how to suppress this feature, does anyone have insights?

thanks