[
https://issues.apache.org/jira/browse/OPENJPA-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712192#action_12712192
]
Michael Dick commented on OPENJPA-1092:
---------------------------------------
I'm guessing it's actually OPENJPA-817 which preserves the order of statements
when using constraint update manager. Absent any other information to the
contrary we'll execute in the order we were called (deletes, updates, and
inserts are grouped - but it's still better than no ordering).
> 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
> 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.
