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:12:35 PST

I'm not sure how optimistic locking could ever prevent dirty-reads for READ_UNCOMMITTED (regardless of when you actually lock()). Then again, maybe others know. James Sutherland from EclipseLink should know for sure.
[Message sent by forum member 'cowwoc' (cowwoc)]

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

This message: [ Message body ]
Next message: glassfish_at_javadesktop.org: "Re: Issue calling POJO in EJB container from connector(JCA)"
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 J"
Reply: glassfish_at_javadesktop.org: "Re: How does an explicit EntityManager.lock() call prevent dirty reads in J"

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