users@glassfish.java.net
Re: How does an explicit EntityManager.lock() call prevent dirty reads in JPA
This message
: [
Message body
] [ More options (
top
,
bottom
) ]
Related messages
: [
Next message
] [
Previous message
] [
In reply to
] [
Next in thread
] [
Replies
]
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:00:18 PST
I suspect that they're leaving the door open to lower isolation levels which need this sort of locking.
[Message sent by forum member 'cowwoc' (cowwoc)]
http://forums.java.net/jive/thread.jspa?messageID=315880
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
]