[eclipselink-users] Using LockModeType.PESSIMISTIC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[eclipselink-users] Using LockModeType.PESSIMISTIC_READ as shared lock in PostgreSQL

From: Andreas Joseph Krogh <andreas@xxxxxxxxxx>
Date: Sat, 18 Jul 2015 17:08:09 +0200 (CEST)
Delivered-to: eclipselink-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-users>
List-help: <mailto:eclipselink-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=unsubscribe>

Hi all.

I'm using PostgreSQL 9.4 with EL-2.6.0

I'm observing that when locking with LockModeType.PESSIMISTIC_READ, EclipseLink issues a "SELECT ... FOR UPDATE"-statement.

I would assume "SELECT ... FOR SHARE" would be used when locking with LockModeType.PESSIMISTIC_READ, and the docs seem to think so too: "LockModeType.PESSIMISTIC_READ represents a shared lock".

Is there a way to make EL issue a "SELECT ... FOR SHARE" lock in an JPQL-query?

Thanks.

Andreas Joseph Krogh

CTO / Partner - Visena AS

Mobile: +47 909 56 963

andreas@xxxxxxxxxx

www.visena.com

Prev by Date: [eclipselink-users] Sequence generator per table in a smooth way?
Next by Date: [eclipselink-users] Orphan Removal not working when, object is added to collection and then same object is removed from collection in same transaction.
Previous by thread: [eclipselink-users] Sequence generator per table in a smooth way?
Next by thread: [eclipselink-users] Orphan Removal not working when, object is added to collection and then same object is removed from collection in same transaction.
Index(es):
- Date
- Thread

Breadcrumbs