You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Andy Jefferson (JIRA)" <ji...@apache.org> on 2009/04/11 21:34:15 UTC

[jira] Assigned: (JDO-629) JPA tests have invalid check for @Temporal field value

     [ https://issues.apache.org/jira/browse/JDO-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Jefferson reassigned JDO-629:
----------------------------------

    Assignee:     (was: Andy Jefferson)

Anyone know where CompletenessTestJPA checks for date fields and how we can swap the check to just check on date (and not time) ? Seems to buried deep within classes.
Other option is to remove the @Temporal annotation, or change it to TIMESTAMP.

> JPA tests have invalid check for @Temporal field value
> ------------------------------------------------------
>
>                 Key: JDO-629
>                 URL: https://issues.apache.org/jira/browse/JDO-629
>             Project: JDO
>          Issue Type: Bug
>          Components: tck2
>    Affects Versions: JDO 2 maintenance release 2
>            Reporter: Andy Jefferson
>             Fix For: JDO 2 maintenance release 3
>
>
> The JPA tests
> companyAnnotatedAllRelationshipsJPAPM.conf
> companyAnnotatedAllRelationshipsJPAConcrete.conf
> companyAnnotatedEmbeddedJPAConcrete.conf
> companyAnnotatedEmbeddedJPAPM.conf
> all have fields annotated with @Temporal(DATE) which means store as java.sql.Date. This will store only the year/month/day components. DataNucleus until recently just stored as a java.util.Date hence storing all details but now obeys the annotation. The check is currently for year/month/day/hour/min/sec yet should be for year/month/day only.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.