users@glassfish.java.net

Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomi

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

From: <glassfish_at_javadesktop.org>
Date: Fri, 14 Nov 2008 12:21:59 PST

With optimistic concurrency, the WHERE clause compare version value to the one at the beginning of the transaction (or the 1st load of an entity), so in T2 it'll check WHERE pk = 1 AND Version = n. And that would fail, right?

Regards,
-marina
[Message sent by forum member 'mvatkina' (mvatkina)]

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

This message: [ Message body ]
Next message: glassfish_at_javadesktop.org: "Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomi"
Previous message: glassfish_at_javadesktop.org: "Re: help initial context for Jndi with Datasource in Glassfish"
In reply to: glassfish_at_javadesktop.org: "Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomi"
Next in thread: glassfish_at_javadesktop.org: "Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomi"
Reply: glassfish_at_javadesktop.org: "Re: EntityManager's forced version update (lock(WRITE) + flush()) not atomi"

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