Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Date: Wed, 30 Mar 2011 15:38:05 +0000 (UTC)
From: "Albert Lee (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Message-ID: 
 <754179320.21536.1301499485719.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1944385411.19202.1301415905684.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Work started] (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


     [ https://issues.apache.org/jira/browse/OPENJPA-1968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on OPENJPA-1968 started by Albert Lee.

> 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, TestDDTimestamp.java
>
>
> 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