openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-1092) enable test case for jpql
Date Wed, 27 May 2009 02:36:45 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713380#action_12713380
] 

Michael Dick commented on OPENJPA-1092:
---------------------------------------

Hi Amy,

Patrick or Abe would be the person (people) to ask about merging OPENJPA-817 to 1.1.x - they're
the release managers for that branch. It would be a change in behavior and 1.1.0 was released
a long time ago, it might be a bit risky to introduce at this time.

I'd be okay with leaving the testcase disabled too, but it's really their call. 

> enable test case for jpql
> -------------------------
>
>                 Key: OPENJPA-1092
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1092
>             Project: OpenJPA
>          Issue Type: Test
>          Components: jdbc
>    Affects Versions: 1.1.0
>         Environment: OS: windows XP professional 
> java version 1.5.0_14 
>            Reporter: Amy Yang
>            Assignee: Michael Dick
>            Priority: Minor
>         Attachments: OPENJPA-1092.patch
>
>
> Currently TestEJBQueryInterface is excluded.
> To enable it, just a little change is needed: invoking em.flush() after every em.persist().
> The test case wants to get the result depends on the order of the creation of the entity
instance. but we (as well as most other JPA implementations) don't care about the creation
order of java instances because the insertion happens when the transaction is committed or
flush is invoked. So adding "em.flush()" after "em.persist()" will resolve the problem.

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


Mime
View raw message