You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@oozie.apache.org by "Alejandro Abdelnur (JIRA)" <ji...@apache.org> on 2011/09/02 01:08:09 UTC

[jira] [Commented] (OOZIE-40) OpenJPA default timestamp type for Postgres has issues

    [ https://issues.apache.org/jira/browse/OOZIE-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095665#comment-13095665 ] 

Alejandro Abdelnur commented on OOZIE-40:
-----------------------------------------

Forcing OpenJPA to use TIMESTAMP instead ABSTIME for java.util.Date properties for Postgres seems to solve the problem.

> OpenJPA default timestamp type for Postgres has issues
> ------------------------------------------------------
>
>                 Key: OOZIE-40
>                 URL: https://issues.apache.org/jira/browse/OOZIE-40
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Alejandro Abdelnur
>            Assignee: Alejandro Abdelnur
>
> OpenJPA uses ABSTIME as the default type for java.util.Date.
> For some odd reason things work fine for a while and then it starts failing with the following exception:
>   "org.postgresql.util.PSQLException: Bad value for type timestamp : invalid" OpenJPA

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira