From dev-return-18826-apmail-openjpa-dev-archive=openjpa.apache.org@openjpa.apache.org Wed Mar 30 15:32:46 2011 Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 71698 invoked from network); 30 Mar 2011 15:32:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Mar 2011 15:32:46 -0000 Received: (qmail 24110 invoked by uid 500); 30 Mar 2011 15:32:46 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 24002 invoked by uid 500); 30 Mar 2011 15:32:46 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 23934 invoked by uid 99); 30 Mar 2011 15:32:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2011 15:32:46 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Mar 2011 15:32:43 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id ACD888A783 for ; Wed, 30 Mar 2011 15:32:05 +0000 (UTC) Date: Wed, 30 Mar 2011 15:32:05 +0000 (UTC) From: "Albert Lee (JIRA)" To: dev@openjpa.apache.org Message-ID: <1588395025.21528.1301499125689.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1944385411.19202.1301415905684.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (OPENJPA-1968) SQLServerDictionery not using DATETIME2 for jdbc driver other than MS JDBC driver MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/OPENJPA-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013020#comment-13013020 ] Albert Lee commented on OPENJPA-1968: ------------------------------------- Even with the current changes in OpenJPA, one may still get the optimistic lock exception due to a problem in the DataDirect 4.2 jdbc driver. A case W103290127 was opened against DataDirect to get this fix. Attached is a test case that reproduce the problem for reference. The problem is openjpa attempts to perform an executeUpdate("DELETE/UPDATE") and the method returns 0 instead of 1 due to timestamp mismatch. As a result, openjpa translates this condition to an optimistic lock exception. > SQLServerDictionery not using DATETIME2 for jdbc driver other than MS JDBC driver > --------------------------------------------------------------------------------- > > Key: OPENJPA-1968 > URL: https://issues.apache.org/jira/browse/OPENJPA-1968 > Project: OpenJPA > Issue Type: Bug > Components: sql > Affects Versions: 2.1.0, 2.1.1, 2.2.0 > Reporter: Albert Lee > Assignee: Albert Lee > Fix For: 2.1.1, 2.2.0 > > Attachments: OPENJPA-1968.patch > > > Use of DATETIME2 db type for Date/Time/Timestamp should based on the SQLServer database version not driver type/vendor. > As a consequence, if version field is a Timestamp data type, you may get optimistic lock exception due to timestamp precision mismatch and hence update to entity may failed. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira