Transaction in stored procedure

[angel]

I have an application in wich a stored procedure executed by a TOracleQuey, insert data into 2 tables, and then commit. after that in a TOracleDataset, that query data from the same tables, I am not able to see new inserted row.
I tried, calling a commit on The TOracleSection and then closing and reopening the TOracleDataset.
The only way to see new data seems to close and then reopen The Session.
Somebody has some idea of this?
I am using doa 3.4 on an oracle 9.2 on a windows 2000 system.

Thanks. Angel

 

[al0]

Looks quite weird. Can you post sample code (or mail it to me)?

Originally posted by angel:
I have an application in wich a stored procedure executed by a TOracleQuey, insert data into 2 tables, and then commit. after that in a TOracleDataset, that query data from the same tables, I am not able to see new inserted row.
I tried, calling a commit on The TOracleSection and then closing and reopening the TOracleDataset.
The only way to see new data seems to close and then reopen The Session.
Somebody has some idea of this?
I am using doa 3.4 on an oracle 9.2 on a windows 2000 system.

Thanks. Angel

 

[Marco Kalter]

Are you using 1 session? In that case you should even see the uncommitted records.

 

[angel]

Yes I am using a session, and the isolation level is read committed, but I call the stored procedure in a TOracleQuery using the same session, in the stored procedure body there is at the end a commit statement. If I query tables from an alredy opened session, in pl/sql. The new data are ready visible.
but in my application, I need close and restart the application to see new data. I already tried to executing a commit in the session of the application, and after that close and reopen the query. But yhis is not working. maybe I have not understood good but I think that read committed isolation level would make visible new data already commited.
Thanks. Angel.

 

[Marco Kalter]

If you use just 1 session, then the isolation level and whether you have committed the inserts does not even matter. Perhaps you can use the Oracle Monitor to verify that the procedure is called and the query is executed as expected.