openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Lee (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OPENJPA-1968) SQLServerDictionery not using DATETIME2 for jdbc driver other than MS JDBC driver
Date Tue, 29 Mar 2011 16:34:05 GMT

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

Albert Lee updated OPENJPA-1968:
--------------------------------

    Attachment: OPENJPA-1968.patch

> 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

Mime
View raw message