Definitely not "works as designed". Sounds like a bug for sure! :-)
I can imagine use cases where one would like nulls included and use
cases where one would like nulls surpressed, in general - but fixing
this is step one!
On 10/6/15 2:52 PM, Jianfeng Jia wrote:
Hi devs,
I hit a failed test case in which I was building a list with the elements
generated from a build-in function, as below,
for $a in [
starts-with("xyz", null),
starts-with("xy", "x")
]
return $a
If any of the elements is Null, it will be omitted in the returned list, e.g.
the above query returns the following result:
[ true
]
However if I explicitly add a null in the list, all the Nulls will be returned.
the following query:
for $a in [
null,
starts-with("xy", null),
starts-with("xy", "x")
]
return $a
will return the expected result:
[ null
, null
, true
]
It applies for other similar functions which returns an option value.
It seems like a bug. Anyone has any ideas about this problem?
Best,
Jianfeng Jia
PhD Candidate of Computer Science
University of California, Irvine
