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
Currently a query only allows a single subquery. This was done to ensure all
variables in the results are always bound.
Having multiple subqueries means a combinatorial 'explosion' in the result set.
Given a query (A) and subqueries (X,Y,Z) where X in turn has subqueries (C,D).
We have the following hierarchy:
?A
?X
?C
?D
?Y
?Z
The result row binds not just a single set of variables now but differs according to the subquery path:
?A * ?X * ?C
?A * ?X * ?D
?A * ?Y
?A * ?Z
Say ?A yields a,b,c and ?Z yields p,q, then for the last bindings alone we get six results:
a p
a q
b p
b q
c p
c q
In spite of the combinatorial explosion, having multiple subqueries may give
necessary flexibility. Most notably, I think we can do away with the concept of
'highlight queries' in visualisation then, as subqueries can take over that role.
The text was updated successfully, but these errors were encountered:
Rather than have just one subquery, multiple will be supported,
separated by a | in the query syntax. This does lead to a combinatorial
explosion, especially if deeply nested and means that not all variables
will be found in the results at all times. It depends on the branch that
is being executed.
Reference: annotation/stam#28
proycon
added a commit
to annotation/stam-rust
that referenced
this issue
Jul 26, 2024
Currently a query only allows a single subquery. This was done to ensure all
variables in the results are always bound.
Having multiple subqueries means a combinatorial 'explosion' in the result set.
Given a query (A) and subqueries (X,Y,Z) where X in turn has subqueries (C,D).
We have the following hierarchy:
The result row binds not just a single set of variables now but differs according to the subquery path:
Say ?A yields a,b,c and ?Z yields p,q, then for the last bindings alone we get six results:
In spite of the combinatorial explosion, having multiple subqueries may give
necessary flexibility. Most notably, I think we can do away with the concept of
'highlight queries' in visualisation then, as subqueries can take over that role.
The text was updated successfully, but these errors were encountered: