This question is locked. New answers and comments are not allowed.
We are using OpenAccess (Ver. 4.3) with Oracle 11.
We find a huge number of statements "set transaction isolation level read committed" fired against the database . Each of them doesn't consume much time, but they sum up to a considerable amount over time.
The statement is not needed, because the default isolation level of the database is "READ COMMITTED" anyway.
Thus we would like to know if it is possible to tell the ORM not to send this statement to the database.
Thank you
Ulrich
We find a huge number of statements "set transaction isolation level read committed" fired against the database . Each of them doesn't consume much time, but they sum up to a considerable amount over time.
The statement is not needed, because the default isolation level of the database is "READ COMMITTED" anyway.
Thus we would like to know if it is possible to tell the ORM not to send this statement to the database.
Thank you
Ulrich
2 Answers, 1 is accepted
0
Hi Ulrich,
Telerik OpenAccess uses the ODP.NET Provider from Oracle to connect to the database. The statements you mentioned are generated by this provider each time a new transaction is opened. I am afraid we cannot influence the provider's behavior in order not to send these statements.
All the best, Ralph
the Telerik team
Telerik OpenAccess uses the ODP.NET Provider from Oracle to connect to the database. The statements you mentioned are generated by this provider each time a new transaction is opened. I am afraid we cannot influence the provider's behavior in order not to send these statements.
All the best, Ralph
the Telerik team
0
Ulrich
Top achievements
Rank 1
Rank 1
answered on 13 May 2011, 09:18 AM
Hi Ralph,
thank you for your answer.
This helps me to look for a solution (if possible) in the ODP.NET Provder.
Best wishes
Ulrich
thank you for your answer.
This helps me to look for a solution (if possible) in the ODP.NET Provder.
Best wishes
Ulrich