false/true/null too special in JSONiq

Bug #1041411 reported by Chris Hillery
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zorba
Fix Released
High
Ghislain Fourny

Bug Description

The following queries compile and run:

my:true

local:false

xyzzy:true

Only bareword true/false/null should work.

(Also, the JSONiq spec does not define whether the default value of jn:jsoniq-boolean-and-null-literals should be true or false. Apparently in Zorba it is "true", and Matthias believes that is good; the spec should reflect this.)

Tags: jsoniq

Related branches

Chris Hillery (ceejatec)
Changed in zorba:
importance: Undecided → High
status: New → Confirmed
assignee: nobody → Ghislain Fourny (gislenius)
Changed in zorba:
status: Confirmed → In Progress
Changed in zorba:
status: In Progress → Fix Committed
milestone: none → 2.7
Till Westmann (tillw)
tags: added: jsoniq
Changed in zorba:
status: Fix Committed → Fix Released
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.