-
Hello!
I'm connecting to Oracle 7.3.4 database from my ASP using ODBC (Microsoft ODBC for Oracle).
There are also several calls to pl/sql proderures from ASP.
My problem is, that after every succesfull pl/sql procedure call changes are commited into database, even if I don't have COMMIT statement in my pl/sql procedure.
I thing that this is done by ODBC.
Does anyone know how to prevent ODBC NOT TO force the commit.
I need this answer very fast .
Thank you,
Tomaz
Instance:
dim db
set db=session("db")
dim comm
Set comm=Server.CreateObject("ADODB.Command")
Set comm.ActiveConnection = db
comm.CommandText = "BEGIN DECLARE p1 VARCHAR2(255); BEGIN p1:=my_procedure('1',526); END; END;"
comm.execute
-
I normally work on SQLServer but maybe on Oracle you can also start a procedure and at the end Commit it. Would that be an option on an oracle database?
-
You can write commit statement in the stored procedure.
But even if I don't call a commit statement in the stored procedure, it is commited when I execute it from ASP.
How can I prevent this procedure from implicit commit.
Best regards,
Tomaz
-
Havent dealt with oracle that much but from what i have seen on the few project i have worked with it always commits wether it runs through odbc or not. The only time you have to commit is when you are in the db itself.
