JSON query startwith operator has unexpected behavior in the face of NULL value

Bug #1745473 reported by Galen Charlton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
New
Medium
Unassigned

Bug Description

As indirectly noted in bug 1745462, the JSON query startwith operator can behave unexpectedly in the face of a NULL/undef argument. For example,

{"where":{"control_set":"1","simple_heading":{"startwith":null},"deleted":"f"},"from":"are","select":{"are":["id"]}}

becomes

SELECT "are".id AS "id" FROM authority.record_entry AS "are" WHERE "are".control_set = '1' AND "are".deleted = 'f' AND "are".simple_heading IS NOT NULL;

A JSON query containing "startwith":null should either be considered a malformed query or, perhaps, turn into "IS NULL".

Evergreen master

Elaine Hardy (ehardy)
tags: added: authority
Elaine Hardy (ehardy)
tags: added: cat-authority
removed: authority
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.