openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Gebala (JIRA)" <j...@apache.org>
Subject [jira] [Created] (OPENJPA-2004) v2.1.0 Type Function Bug
Date Tue, 24 May 2011 17:19:47 GMT
v2.1.0 Type Function Bug
------------------------

                 Key: OPENJPA-2004
                 URL: https://issues.apache.org/jira/browse/OPENJPA-2004
             Project: OpenJPA
          Issue Type: Bug
          Components: query
    Affects Versions: 2.1.0
         Environment: Linux and OS X.
            Reporter: Brian Gebala
            Priority: Minor
             Fix For: 2.1.1


I just updated to v2.1.0 from v2.0.1 and noticed that a query using TYPE()
<> X is no longer working. I have an abstract base class and two
subclasses. My query asks for all but one of the subclasses, like this:

SELECT d FROM AbstractClass d WHERE d._state = :state AND TYPE(d) <>
SubClassTwo

When I run this query with v2.1.0, the SQL is generated as if the query
said
"TYPE(d) = SubClassTwo", resulting in a match on
the SubClassTwo discriminator. I found a work-around using NOT IN:

SELECT d FROM AbstractClass d WHERE d._state = :state AND TYPE(d) NOT IN
(SubClassThree)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message