[
https://issues.apache.org/jira/browse/OPENJPA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653367#action_12653367
]
Albert Lee commented on OPENJPA-433:
------------------------------------
I don't think the configuration framework be smart enough to recognize the
DBDictionary's static symbollic constants as the property value.
"datePricision" is of type int. One can use int, Integer or String type value
to set this dictionary attribute.
Albert Lee.
> Timestamp rounded upon database updating
> ----------------------------------------
>
> Key: OPENJPA-433
> URL: https://issues.apache.org/jira/browse/OPENJPA-433
> Project: OpenJPA
> Issue Type: Bug
> Components: sql
> Affects Versions: 1.0.0
> Environment: Postgresql dictionary; unsure if others are affected
> Reporter: Nick Johnson
> Priority: Minor
>
> When updating a Timestamp field, OpenJPA is rounding the time to the nearest
> hundredth of a second. For example, in this case I print the Timestamp to
> stdout just before committing the transaction. Note the difference between
> the printed time and the time given in the SQL:
> New time is 2007-11-04 21:16:49.906
> 4593 tally_ho TRACE [main] openjpa.jdbc.SQL - <t 1205211, conn 6232809>
> executing prepstmnt 8529229 UPDATE Article SET create_date = ? WHERE
> object_id = ? [params=(Timestamp) 2007-11-04 21:16:49.91, (long) 1]
> This is actually causing a unit test of mine (one which checks that the
> create_date field updates correctly) to fail. It's fairly easy to kludge
> around for now.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
