EclipseLink namedQuery NULL parameter passed as '=NULL', fails to return rowset
Last updated on OCTOBER 27, 2014
Applies to:Oracle TopLink - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 12c]
Information in this document applies to any platform.
When upgrading a Weblogic Kodo persistence application to EclipseLink, an issue is noted with named queries using parameters that have NULL values. If a parameter is specified as IS NULL, a select statement always returns an empty result back with EclipseLink even though there are the records in the database. It is noted that the same query returns records in Kodo.
For example an entity with some fields that are nullable and a named query that uses them in the query:
If :shareCashBoxId IS NULL the above select statement always return an empty result back with EclipseLink even though there are the records in the database.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms