Return-Path: 
 <open-jpa-dev-return-3182-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 1607 invoked from network); 5 Apr 2007 19:45:54 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 5 Apr 2007 19:45:54 -0000
Received: (qmail 46769 invoked by uid 500); 5 Apr 2007 19:46:01 -0000
Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org
Received: (qmail 46733 invoked by uid 500); 5 Apr 2007 19:46: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 46724 invoked by uid 99); 5 Apr 2007 19:46:00 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Apr 2007 12:46: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; Thu, 05 Apr 2007 12:45:53 -0700
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id 1F5E8714070
	for <open-jpa-dev@incubator.apache.org>;
 Thu,  5 Apr 2007 12:45:33 -0700 (PDT)
Message-ID: <23257387.1175802333125.JavaMail.jira@brutus>
Date: Thu, 5 Apr 2007 12:45:33 -0700 (PDT)
From: "Abe White (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_12487085 ] 

Abe White commented on OPENJPA-182:
-----------------------------------

>  I know that Oracle allows you to add a FOR UPDATE clause to a query, and this affects the results of that query. In Sun appserver CMP we use this to set exclusive locks on rows where we want pessimistic locking behavior just for certain tables.

Again, this is exactly what our existing lock levels and APIs do.  

> 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.