[
https://issues.apache.org/jira/browse/OPENJPA-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-636.
-------------------------------------
Resolution: Fixed
Already fixed on master: ref_guide_dbsetup.adoc:455-470 documents DatePrecision
rounding and DateMillisecondBehavior, and supported_databases.adoc:659,667
covers per-database precision loss and its effect on Timestamp version fields.
There is no single overview topic, but the content the issue asked for is in
the manual. Closing.
> Clarify impedance mismatch between in-memory objects and their persistent
> counterparts
> --------------------------------------------------------------------------------------
>
> Key: OPENJPA-636
> URL: https://issues.apache.org/jira/browse/OPENJPA-636
> Project: OpenJPA
> Issue Type: Improvement
> Components: docs
> Environment: All
> Reporter: Tim Holloway
> Priority: Minor
>
> Date objects persisted out and read back may not have exactly identical
> values due to differences in the implicit precision of Java date object
> versus the actual database. The results can be quite frustrating to
> developers who aren't aware of that fact.
> A discussion of this problem can be found here:
> http://saloon.javaranch.com/cgi-bin/ubb/ultimatebb.cgi?ubb=get_topic&f=78&t=004041&p=1
> I think it deserves to be a topic in the user's guide, along with mention of
> similar imprecise datatypes.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
