Affects Version/s: 2.2.0
Fix Version/s: 2.3.0
We hit a problem that OpenJPA always rounds to the nearest 10ms for PostgreSQL. We found the following old issue in which a workaround got outlined in
But still the question remains: PostgreSQL is perfectly fine to store milliseconds, so why does the PostgresDictionary line 146 sets:
> datePrecision = CENTI;
The generated TIMESTAMP type in PostgreSQL should even be able to store microseconds! 
And that seems to be the case since quite some time now (1999) .
I'm really tempted to set this to MICRO; Anyone against it?
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|2h 30m||1||Mark Struberg||26/Apr/12 15:11|
|1136d 6h 8m||1||Mark Struberg||06/Jun/15 21:19|