Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <1954191520.1243016565643.JavaMail.jira@brutus>
Date: Fri, 22 May 2009 11:22:45 -0700 (PDT)
From: "Michael Dick (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Assigned: (OPENJPA-1092) enable test case for jpql
In-Reply-To: <1054012932.1242629446270.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Michael Dick reassigned OPENJPA-1092:
-------------------------------------

    Assignee: Michael Dick

> 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.