users@glassfish.java.net

Re: How does an explicit EntityManager.lock() call prevent dirty reads in JPA

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]

From: <glassfish_at_javadesktop.org>
Date: Mon, 10 Nov 2008 12:06:07 PST

OK, then let's assume READ_UNCOMMITED, the next and last lower isolation level. How would the lock() int T1 prevent T2 from commiting after a dirty-read as in the scenario exposed in the first post?

Thanks.
[Message sent by forum member 'vladbalan' (vladbalan)]

http://forums.java.net/jive/thread.jspa?messageID=315881

This message: [ Message body ]
Next message: glassfish_at_javadesktop.org: "Re: How does an explicit EntityManager.lock() call prevent dirty reads in JPA"
Previous message: glassfish_at_javadesktop.org: "Re: How does an explicit EntityManager.lock() call prevent dirty reads in JPA"
In reply to: glassfish_at_javadesktop.org: "Re: How does an explicit EntityManager.lock() call prevent dirty reads in JPA"
Next in thread: glassfish_at_javadesktop.org: "Re: How does an explicit EntityManager.lock() call prevent dirty reads in JPA"
Reply: glassfish_at_javadesktop.org: "Re: How does an explicit EntityManager.lock() call prevent dirty reads in JPA"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]