Return-Path: 
 <open-jpa-dev-return-3139-apmail-incubator-open-jpa-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org
Received: (qmail 47142 invoked from network); 4 Apr 2007 23:59:53 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 4 Apr 2007 23:59:53 -0000
Received: (qmail 73304 invoked by uid 500); 5 Apr 2007 00:00:00 -0000
Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org
Received: (qmail 73271 invoked by uid 500); 5 Apr 2007 00:00:00 -0000
Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:open-jpa-dev-help@incubator.apache.org>
List-Unsubscribe: <mailto:open-jpa-dev-unsubscribe@incubator.apache.org>
List-Post: <mailto:open-jpa-dev@incubator.apache.org>
List-Id: <open-jpa-dev.incubator.apache.org>
Reply-To: open-jpa-dev@incubator.apache.org
Delivered-To: mailing list open-jpa-dev@incubator.apache.org
Received: (qmail 73257 invoked by uid 99); 5 Apr 2007 00:00:00 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Apr 2007 17:00:00 -0700
X-ASF-Spam-Status: No, hits=-100.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Apr 2007 16:59:52 -0700
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 40E0D714066
	for <open-jpa-dev@incubator.apache.org>;
 Wed,  4 Apr 2007 16:59:32 -0700 (PDT)
Message-ID: <4796195.1175731172232.JavaMail.jira@brutus>
Date: Wed, 4 Apr 2007 16:59:32 -0700 (PDT)
From: "Craig Russell (JIRA)" <jira@apache.org>
To: open-jpa-dev@incubator.apache.org
Subject: [jira] Commented: (OPENJPA-182) db2 update lock syntax  WITH
 <isolation> USE AND KEEP UPDATE LOCKS
In-Reply-To: <10767081.1174929812132.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


    [ https://issues.apache.org/jira/browse/OPENJPA-182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486812 ] 

Craig Russell commented on OPENJPA-182:
---------------------------------------

A use-case for the isolation level is to support different locking semantics for different classes and possibly for different queries. To use Patrick's patch would I need to use a different fetch plan before issuing a find or a query and then set it back after that method call? Or can I specify an isolation level in the FetchConfiguration per class?

> db2 update lock syntax  WITH <isolation> USE AND KEEP UPDATE LOCKS
> ------------------------------------------------------------------
>
>                 Key: OPENJPA-182
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-182
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: jdbc
>         Environment: db2 database driver for zOS, AS400, Unix, Windows, Linux
>            Reporter: David Wisneski
>         Assigned To: David Wisneski
>         Attachments: OPENJPA-182.patch, openJPA182.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.