Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 76579 invoked from network); 9 Oct 2008 13:57:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Oct 2008 13:57:52 -0000 Received: (qmail 46024 invoked by uid 500); 9 Oct 2008 13:57:49 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 46003 invoked by uid 500); 9 Oct 2008 13:57:49 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 45992 invoked by uid 99); 9 Oct 2008 13:57:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2008 06:57:49 -0700 X-ASF-Spam-Status: No, hits=2.7 required=10.0 tests=DNS_FROM_OPENWHOIS,DNS_FROM_SECURITYSAGE,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2008 13:56:44 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Knw12-0002PD-C9 for user-java@ibatis.apache.org; Thu, 09 Oct 2008 06:57:20 -0700 Message-ID: <19899543.post@talk.nabble.com> Date: Thu, 9 Oct 2008 06:57:20 -0700 (PDT) From: mule_user To: user-java@ibatis.apache.org Subject: Re: IBATIS 2.3.3, JDK 1.5 - Optimistic locking strategies In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: sgho@aol.com References: <19867989.post@talk.nabble.com> <19884010.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org My fundamental question was: Is there a way to achieve optimistic locking using timestamp attribute, if the "OldObject" and/or the update timestamp of the old object is available in scope. All the solutions require you to keep the "OldObject" in scope because, the where clause; requires you to pass the ID of the "OldObject" and update timestamp of the "OldObject". Otimistic locking requires keeping "OldObject" in scope. I was hoping that there could be another solution using iBATIS where I do not have to keep "OldObject" in scope. -- View this message in context: http://www.nabble.com/IBATIS-2.3.3%2C-JDK-1.5---Optimistic-locking-strategies-tp19867989p19899543.html Sent from the iBATIS - User - Java mailing list archive at Nabble.com.