[
https://issues.apache.org/jira/browse/OPENJPA-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713363#action_12713363
]
Amy Yang commented on OPENJPA-1092:
-----------------------------------
Hi Michael,
thank you very much. Got it.
my last question: is it feasible to merge fix of OPENJPA-817 to branch 1.1.x?
if statement batching support is introduced in the 1.2.x branch, maybe it's ok
to let the test case disabled in 1.1.x.
> 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.