You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
There is a bug where operations with the not() operator does not behave according to expectation.
When querying for document, I often want to select only documents, not subdocuments. I often forget that rdf:nil is not treated the same way when using the not() construct.
Here are the four cases, of which I think the last one misbehaves, and should work the same as number 3. My reasoning is that the handling in example 2 and example 4 should work the same way, just in the inverse. The reason I think that this is a bug, at least it goes against expectations, when running example 1, the v:unbound variable is set to rdf:nil.
Find all subdocuments, returns expected documents (with unbound variable)
Describe the bug
There is a bug where operations with the
not()
operator does not behave according to expectation.When querying for document, I often want to select only documents, not subdocuments. I often forget that
rdf:nil
is not treated the same way when using thenot()
construct.Here are the four cases, of which I think the last one misbehaves, and should work the same as number 3. My reasoning is that the handling in example 2 and example 4 should work the same way, just in the inverse. The reason I think that this is a bug, at least it goes against expectations, when running example 1, the
v:unbound
variable is set tordf:nil
.To Reproduce
Steps to reproduce the behavior:
Expected behavior
The expectation is that the result of example 3 and example 4 should be the same.
Screenshots
N/A
Info (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: