[eclipselink-dev] bug 327472 - testPESSMISTIC

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

[eclipselink-dev] bug 327472 - testPESSMISTIC_ES5

From: "Goerler, Adrian" <adrian.goerler@xxxxxxx>
Date: Fri, 22 Oct 2010 09:19:13 +0200
Accept-language: en-US, de-DE
Acceptlanguage: en-US, de-DE
Delivered-to: eclipselink-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-dev>
List-help: <mailto:eclipselink-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-dev>, <mailto:eclipselink-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-dev>, <mailto:eclipselink-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: ActxuW2kmpkxzkZ5QMiFpbfOkY0+sQ==
Thread-topic: bug 327472 - testPESSMISTIC_ES5

Hi,

https://bugs.eclipse.org/bugs/show_bug.cgi?id=327472

this issue is due to a particularity in the order, which MaxDB uses to lock tables in the presence of FK constraints. Seems that MaxDB can't change this.

I am proposing to use a native query on MaxDB to assert that pessimistic locking with lock scope EXTENDED guarantees repeatable read on the join table (as required by the spec).

Could you please have a look?

Thanks,

Adrian

Adrian Görler
SAP AG

Pflichtangaben/Mandatory Disclosure Statements:
http://www.sap.com/company/legal/impressum.epx

Prev by Date: [eclipselink-dev] BUILD STATUS:: trunk nightly build has test failures!
Next by Date: [eclipselink-dev] SessionBroker JPA support Wiki design doc.
Previous by thread: [eclipselink-dev] fix for bug 328293 checked in
Next by thread: [eclipselink-dev] SessionBroker JPA support Wiki design doc.
Index(es):
- Date
- Thread

Breadcrumbs