Hi all,
what's your opinion on this issue?
In general MaxDB seems to get along well with a lock timeout of 0, which we can translate to NOWAIT.
However, if applied to an entity with inheritance type JOINED, the lock NOWAIT fails as two SELECTs - a non-locking-SELECT to determine the discriminator preceeded by a locking-NOWAIT-SELECT to fetch and lock the data are executed. The lock method will
possibly wait on the first SELECT. This issue causes the test testLockWithJoinedInheritanceStrategy to fail.
TestLockWithJoinedInheritanceStrategy is part of the JPA SRG, hence I am reluctant just to skip it. However, this test (as most of the pessimistic locking tests) is skipped on
isFirebird() || platform.isH2()
|| platform.isHSQL() || platform.isAccess() || platform.isSQLAnywhere() || platform.isDerby() || platform.isPostgreSQL() || platform.isSymfoware())
hence I would not be overly ashamed to skip it on MaxDB as well.
Would you object if I add a skip for this test on MaxDB?
-Adrian
SAP AG
Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany
Sitz der Gesellschaft/Registered Office: Walldorf, Germany
Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Léo Apotheker (stellvertretender Sprecher/Deputy CEO), Werner Brandt, Claus Heinrich, Gerhard Oswald, John Schwarz, Peter Zencke
Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner
Registergericht/Commercial Register Mannheim No HRB 350269
