Wednesday, 15 August 2012

sql - JPA reading data with NO LOCK -


In the application we are writing, it is necessary that we with (NOLOCK) Just do not take that question for so long in the process.

I have not got anything to accomplish this. How I have found out how to enable optimistic or pessimistic locking, but as far as I know, that is to write data, not to read.

Is there any way to do this?

We are using the Jpeg and Criteria APIs connecting to an MSSQL server and the application server is Glassfish 4.

Erates

with (NOLOCK) READ-UNCOMMITED transactions are very similar to working at isolation level, because it has been explained. Given this, you can get what you want by using the configured DB connection in that transaction level. If you want to decide during execution, which transaction level will be used to simplify and change transaction isolation level (after which you should change it at the original level).

If you use (NOLLOCK) to avoid some bugs, there is a facility for a different goal, then you must write native questions for that


Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)