db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "bernard (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5728) Add Support for NULL IS NULL
Date Wed, 25 Apr 2012 22:54:17 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262224#comment-13262224

bernard commented on DERBY-5728:

I think it it is different because it is more narrow in scope, it is an enhancement not a
bug and does not leave open the question whether it might be an ORM bug that needs to be resolved.
I hope this issue is easier to resolve.
> Add Support for NULL IS NULL
> ----------------------------
>                 Key: DERBY-5728
>                 URL: https://issues.apache.org/jira/browse/DERBY-5728
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions:
>         Environment: Windows XP
> java version "1.6.0_31"
> Java(TM) SE Runtime Environment (build 1.6.0_31-b05)
> Java HotSpot(TM) Client VM (build 20.6-b01, mixed mode, sharing)
>            Reporter: bernard
>            Priority: Critical
>         Attachments: NullParameterEclipseLinkDerbyMaven.zip, NullParameterHibernateDerbyMaven.zip
> The following query fails:
> Why this is an issue?
> At least two major Java ORMs, Hibernate JPA and EclipseLink JPA have isues with generating
SQL for trivial JPQL queries such as:
> select object(c) from Customer c where ((name: is null) or (c.name = name:))
> where name: is a parameter
> For why this is a fundamental issue, please see a minimalistic JPQL query at
> http://en.wikipedia.org/wiki/Java_Persistence_Query_Language#Examples 
> Part of this has already been resolved by issue "Add support for setObject(<arg>,
> https://issues.apache.org/jira/browse/DERBY-1938
> Please see EclipseLink and Hibernate test cases for verification.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message