Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <32409084.1186593899406.JavaMail.jira@brutus>
Date: Wed, 8 Aug 2007 10:24:59 -0700 (PDT)
From: "Patrick Linskey (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Updated: (OPENJPA-187) MEMBER OF query fails on OpenJPA, but
 works fine with TopLink and Hibernate EM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Patrick Linskey updated OPENJPA-187:
------------------------------------

    Fix Version/s:     (was: 1.0.0)
       Issue Type: New Feature  (was: Bug)

I think that this is a new feature request, not a bug. It sounds like a neat feature, but I do not think that it's required behavior per the spec, and probably has an easy workaround (look up the instance first).

> MEMBER OF query fails on OpenJPA, but works fine with TopLink and Hibernate EM
> ------------------------------------------------------------------------------
>
>                 Key: OPENJPA-187
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-187
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: query
>    Affects Versions: 0.9.7
>            Reporter: Jacek Laskowski
>
> What's wrong with the following query?
>   Query query = em.createQuery("SELECT DISTINCT o FROM Osoba o WHERE :projekt MEMBER OF o.projekty");
>   query.setParameter("projekt", new Projekt("Apache OpenEJB", RodzajProjektu.OTWARTY));
>   List<Osoba> osoby = query.getResultList();
>   assert osoby.size() == 1 : "Otrzymano " + osoby.size();
> where Projekt is an entity where @Id is of type String (the first input parameter in the two-param constructor above).
> TopLink 2.0 BUILD 40 and Hibernate EntityManager 3.3.0.GA work fine whereas OpenJPA 0.9.7-SNAPSHOT finishes with the java.lang.AssertionError error (it's the test itself actually, but since the query returns 0 elements the issue originates in OpenJPA).

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