users@glassfish.java.net
Re: How does an explicit EntityManager.lock() call prevent dirty reads in J
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
: Tue, 11 Nov 2008 18:12:03 PST
Good catch! Too bad the Javadoc doesn't mention this only works for READ_COMMITTED.
[Message sent by forum member 'cowwoc' (cowwoc)]
http://forums.java.net/jive/thread.jspa?messageID=316189
This message
: [
Message body
]
Next message
:
glassfish_at_javadesktop.org: "Re: Is Glassfish 9.1 supported MS SQL Server 2008?"
Previous message
:
glassfish_at_javadesktop.org: "Re: How does an explicit EntityManager.lock() call prevent dirty reads in J"
In reply to
:
glassfish_at_javadesktop.org: "Re: How does an explicit EntityManager.lock() call prevent dirty reads in J"
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
]