-
Notifications
You must be signed in to change notification settings - Fork 25
SPARQL 1.0: variable introduced by GRAPH is not affecting inner OPTIONAL #230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Scoping is already tested but this is an easy mistake when trying to optimize such queries
| ] ; | ||
| mf:result <graph-variable-join.ttl> ; | ||
| . | ||
| :graph-optional rdf:type mf:QueryEvaluationTest ; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't in the list of tests at mf:entries so it does not run.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Fixed.
| rs:binding [ rs:value <data-variable-join.ttl> ; | ||
| rs:variable "http://example/s2" | ||
| ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks wrong. The variable is s.
I think the right answer is:
| rs:binding [ rs:value <data-variable-join.ttl> ; | |
| rs:variable "http://example/s2" | |
| ] | |
| rs:binding [ rs:value <data-optional.ttl> ; | |
| rs:variable "s" | |
| ] |
that is:
-----------------------------
| g | s |
============================
| <data-optional.ttl> | :s2 |
-----------------------------
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, got confused. Fixed. Thanks for spotting
Scoping is already tested but this is an easy mistake when trying to optimize such queries