Community
Participate
Working Groups
The test testLockWithJoinedInheritanceStrategy fails on MaxDB: MaxDB uses isolation level READ COMITTED. In order lock an entity with inheritance type JOINED, EclipseLink executes two statements: - a non-locking SELECT to determine the discriminator value - a locking SELECT (with NOWAIT) to fetch the data On MaxDB, the first select waits. Hence, effectively, the entire lock operation will although a lock timeout of 0 (NOWAIT) is specified.
Theroretically, it seems to be possible to fetch (or lock) the data in case of inheritance type JOINED using single statement using OUTER JOINs. Also, one could imagine that the first SELECT, which determines the discriminator, already places the lock (NOWAIT).
Created attachment 180644 [details] skip this test on MaxDB Tested on MaxDB
Reviewed by Tom. Tested on MaxDB. Checked in at #8351.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
