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 09:06:05 PST

I'd also add that your example isn't matching the javadoc "phaenomena" P1:
it says that the [u]read is taking place after an edit[/u]. In your example T1 (it doesen't matter that you inversed them) does not perform a read after T2's edit.
[Message sent by forum member 'vladbalan' (vladbalan)]

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

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"

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