[#OPENJPA-182] db2 update lock syntax WITH <isolation> USE AND KEEP UPDATE LOCKS

OpenJPA

db2 update lock syntax WITH <isolation> USE AND KEEP UPDATE LOCKS

Created: 26/Mar/07 05:22 PM Updated: 18/Apr/07 08:22 PM

Return to search

Component/s:

jdbc

Affects Version/s:

None

Fix Version/s:

0.9.7

Time Tracking:

Not Specified

File Attachments:

File Name	Date Attached	Attached By	Size
JIRA182-subselect.patch	2007-04-17 09:43 PM	Ritika Maheshwari	3 kB
OPENJPA-182.patch	2007-04-06 06:45 PM	Patrick Linskey	4 kB
OPENJPA-182.patch	2007-04-04 11:49 PM	Patrick Linskey	14 kB
openJPA182.patch	2007-03-28 09:58 PM	Ritika Maheshwari	13 kB
openjpa182TestCase.jar	2007-04-05 09:06 PM	Ritika Maheshwari	1 kB

Environment:

db2 database driver for zOS, AS400, Unix, Windows, Linux

Issue Links:

Reference

This issue relates to:

~~OPENJPA-222~~ FOR READ ONLY clause getting generated for subselects

Resolution Date:

06/Apr/07 11:54 PM

Description

« Hide

A while back we changed the syntax of update locking from FOR UPDATE OF to WITH RS USE AND KEEP UPDATE LOCKS. Additional changes are required because
1. if isolation=serializable is configured, then the syntax should be WITH RR USE AND KEEP UDPATE LOCKS
2. when using DB2/400 on iSeries machines, the syntax is WITH RS USE AND KEEP EXCLUSIVE LOCKS or WITH RR USE AND KEEP EXCLUSIVE LOCKS because DB2/400 only supports read or exclusive locks.
3. DB2 supports both a FETCH FIRST ROWS and update LOCKS clauses.

So we change supportsLockingWithSelectRange = true in the AbstractDB2Dictionary class and change the DB2Dictionary to append the correct LOCKS syntax depending on vendor, release and isolation level.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

No work has yet been logged on this issue.