[
https://issues.apache.org/jira/browse/OPENJPA-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-638.
-------------------------------------
Resolution: Won't Fix
Closing as obsolete during backlog cleanup: Float timestamps were a PostgreSQL
build option that was removed in PostgreSQL 10, which only stores integer
microseconds. Millisecond Java values therefore round-trip exactly. Please
reopen if this still happens with OpenJPA 4.x.
> Timestamp unsuitable for versioning on PostgreSQL databases
> -----------------------------------------------------------
>
> Key: OPENJPA-638
> URL: https://issues.apache.org/jira/browse/OPENJPA-638
> Project: OpenJPA
> Issue Type: Bug
> Components: docs
> Environment: PostgreSQL ca Version 8, Section 2.17 of the Apache
> OpenJPA User's Guide.
> Reporter: Tim Holloway
> Priority: Major
>
> PostgreSQL can store objects in its native timestamp in a format determined
> by PostgreSQL build options. By default, the postgresql timestamp is a
> double-precision floating-point number with maximum precision of 6 digits
> (see section 8.4 of the PostgreSQL 8.2.7 documentation). java.sql.Timestamp
> extends java.util.Date, and thus stores data in long integer milliseconds.
> The resulting value mismatch can cause optimistic updates to fail.
> See also Jira issue OpenJPA-636.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
