openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Struberg (JIRA)" <>
Subject [jira] [Commented] (OPENJPA-2178) PostgresDictionary
Date Thu, 26 Apr 2012 14:48:16 GMT


Mark Struberg commented on OPENJPA-2178:

postgresql-6.3 was in 1998 I honestly do not expect that we need to implement that. 
And even if so: they can still use the trick outlined in OPENJPA-433, but now just do it the
other way around.

If someone really has such an old postgresql or likes to round to 1/100 seconds for another
reason, he could still add the following setting:

<property name="openjpa.jdbc.DBDictionary" value="DatePrecision=CENTI"/>
> PostgresDictionary 
> -------------------
>                 Key: OPENJPA-2178
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 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 OPENJPA-433
> 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) [2].
> I'm really tempted to set this to MICRO; Anyone against it?
> [1]
> [2]

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message