Return-Path: Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: (qmail 56605 invoked from network); 14 Apr 2011 13:34:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Apr 2011 13:34:03 -0000 Received: (qmail 58629 invoked by uid 500); 14 Apr 2011 13:34:02 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 58596 invoked by uid 500); 14 Apr 2011 13:34:02 -0000 Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@openjpa.apache.org Delivered-To: mailing list users@openjpa.apache.org Received: (qmail 58588 invoked by uid 99); 14 Apr 2011 13:34:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Apr 2011 13:34:02 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of michael.d.dick@gmail.com designates 209.85.213.174 as permitted sender) Received: from [209.85.213.174] (HELO mail-yx0-f174.google.com) (209.85.213.174) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Apr 2011 13:33:56 +0000 Received: by yxs7 with SMTP id 7so881725yxs.33 for ; Thu, 14 Apr 2011 06:33:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=n/zRycF3Y+RHFAiYsOvsC4X7Qn8AVKP4LYI/90uCtmc=; b=b5/OyAyHW9kg4v7kUqd0jSz56ToVafNE8G+k0aZczhJgo4kcLymAwQaUmQQUliTmTX Q1hud0nIhadmgfjcAjJyHMYS49Ho/OSY6HaYwi++3zwsOzj6MPW2KoqgGfCwHOtBMMEm szClZgr0ch5UdBNpYUFz5wWtxZ0ybtDFq7xnI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=xTlE4T7OSUEwVVNl5Rj4w0/Dd3u5nbOwQvZyb6Y3ctfCzS5iQ15Nrt665jMknYzNwr G1H1qjjAlX3NxTspeNuUyg7aDuHpZfD7UmbRCGJdibRQ5AYT/mwTrCUqyTdGx+yXOXGY dSJO89nhh4xsa81iwGfsu6FOGFaS8bTdztLlA= Received: by 10.91.201.11 with SMTP id d11mr1355310agq.111.1302788015096; Thu, 14 Apr 2011 06:33:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.90.192.17 with HTTP; Thu, 14 Apr 2011 06:33:15 -0700 (PDT) In-Reply-To: <1302706892785-6269353.post@n2.nabble.com> References: <1302654019826-6267241.post@n2.nabble.com> <1302706892785-6269353.post@n2.nabble.com> From: Michael Dick Date: Thu, 14 Apr 2011 08:33:15 -0500 Message-ID: Subject: Re: @Version for sqlserver "timpstamp" datatype To: users@openjpa.apache.org Cc: chintan4181 Content-Type: multipart/alternative; boundary=001636af0255db824504a0e0f81a X-Virus-Checked: Checked by ClamAV on apache.org --001636af0255db824504a0e0f81a Content-Type: text/plain; charset=ISO-8859-1 Hi Chintan, I'm not very familiar with SQLServer, and I can't recommend a JDBC driver. It's possible that DataDirect or Microsoft have other workarounds that will convert a timestamp to another Java type, but it's probably unlikely. If you cannot introduce a new column it's very hard to do optimistic locking. I'm sorry I don't have a good solution for this problem. Maybe someone else on the list will have a better idea. -mike On Wed, Apr 13, 2011 at 10:01 AM, chintan4181 wrote: > Thanks Mike. are you aware of any mssql jdbc driver which maps timestamp to > java.sql.TimeStamp? becuase i can not introduce new version column in > existing db. > > can youplease guide me any other way to implement optimistic locking? > > ~chintan > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Version-for-sqlserver-timpstamp-datatype-tp6267241p6269353.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. > --001636af0255db824504a0e0f81a--