db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernard (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-5629) Queries with guarded null Parameter fail
Date Fri, 24 Feb 2012 04:49:49 GMT
Queries with guarded null Parameter fail

                 Key: DERBY-5629
                 URL: https://issues.apache.org/jira/browse/DERBY-5629
             Project: Derby
          Issue Type: Bug
          Components: JDBC
    Affects Versions:
         Environment: java version "1.6.0_30"
Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
Java HotSpot(TM) Client VM (build 20.5-b03, mixed mode, sharing)
            Reporter: Bernard

Some test cases in the attached Maven project fail where a null parameter is passed in or
a null value is coded in the query.

In the context of this issue, a recently closed issue appears to be relevant:

"Add support for setObject(<arg>, null)"

Some test cases in the attached project are Hibernate JPQL cases where Hibernate takes care
of generating the SQL queries.

I thought it was appropriate to make a few cases not only one so that the issue gets a little
more test coverage.

I also assume that issue DERBY-1938 aims to fix what we can see in these cases.

This has become a major issue because it causes failure of a minimalistic JPQL query as shown


that shows a JPQL query:

SELECT a FROM Author a WHERE :lastName IS NULL OR LOWER(a.lastName) = :lastName

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