Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: 10.8.2.2
    • Fix Version/s: None
    • Component/s: SQL
    • 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)
    • Urgency:
      Urgent

      Description

      The following query fails:

      SELECT ID FROM CUSTOMER WHERE ((NULL IS NULL) OR (NAME = NULL))

      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>, null)"
      https://issues.apache.org/jira/browse/DERBY-1938

      Please see EclipseLink and Hibernate test cases for verification.

        Issue Links

          Activity

          Hide
          bernard added a comment -

          EclipseLink Test Case

          Show
          bernard added a comment - EclipseLink Test Case
          Hide
          bernard added a comment -

          Hibernate Test Case

          Show
          bernard added a comment - Hibernate Test Case
          Hide
          Knut Anders Hatlen added a comment -

          Hi Bernard,

          Is this problem different from the one you reported in DERBY-5629?

          Show
          Knut Anders Hatlen added a comment - Hi Bernard, Is this problem different from the one you reported in DERBY-5629 ?
          Hide
          bernard added a comment -

          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.

          Show
          bernard added a comment - 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.

            People

            • Assignee:
              Unassigned
              Reporter:
              bernard
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Development