Conversation
| syntax forms `EXISTS {P}` or `NOT EXISTS {P}`, | ||
| any variable that is in-scope for `GP` is | ||
| also in-scope for all group graph patterns, | ||
| basic graph patterns, and paths inside `P`. |
There was a problem hiding this comment.
"...also in-scope for all group graph patterns, basic graph patterns, and paths inside P"
Does this mean only in-scope if P is precisely a group graph pattern, basic graph pattern, or path?
Or does it allow nesting? E.g. within optional or service?
There was a problem hiding this comment.
Nesting - any group graph pattern.
The requirement is to include the variables of the current row at the bottom then they get incorporated all the way up to P by the usual rules.
| <p> | ||
| Syntax forms `EXISTS` or `NOT EXISTS` appear inside | ||
| a `FILTER` and filters appear inside group graph patterns. | ||
| Let `F` be a syntax form `FILTER` |
There was a problem hiding this comment.
F is not used anywhere after. Is it intentional?
There was a problem hiding this comment.
No, it's not intentional. (See Greg's comment).
It is trying to say that scope is modified only for the leaves of the AST that can set variables - BGPs and paths.
From there, the current row variables is in-scope by the usual rules and include the current row.
I'll revise it.
| </tbody> | ||
| </table> | ||
| <p> | ||
| Syntax forms `EXISTS` or `NOT EXISTS` appear inside |
There was a problem hiding this comment.
This seems overly restrictive in suggesting that (not) exists only appears inside filters (and not other places where expressions can be used).
There was a problem hiding this comment.
Is this change enough?
"inside a FILTER and filters appear inside group graph patterns."
==>
"inside expressions <link to [127] Expression>."
Or something that enumerates the places that expressions occur, filter, AS, ORDER BY, (GROUP BY and HAVING are allow AS).
There was a problem hiding this comment.
Expression would be good, I think.
e09d5a4 to
726cb67
Compare
Preview | Diff