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
Even if the algebra generator is changed to cope with the non-parser AST generated by querybuilder (PR #2155), should the querybuilder try to generate parser-compatible ASTs?
When used over the wire, a query is always in string form.
afs
changed the title
Querybuilder should generate query syntax trees that correspond to parser output.
QueryBuilder should generate query syntax trees that correspond to parser output.
Jan 14, 2024
Version
5.0.0
Feature
See #2153 and #2155 .
Even if the algebra generator is changed to cope with the non-parser AST generated by querybuilder (PR #2155), should the querybuilder try to generate parser-compatible ASTs?
When used over the wire, a query is always in string form.
Example (Jena 4.10.0):
Output:
Note the slight difference in the query strings due to the presence of the ElementGroup in the second, parsed case, which isn't in querybuilder form.
The query patterns of the WHERE clause are:
ElementFilter(true)
ElementGroup ( ElementFilter(true) )
.Are you interested in contributing a solution yourself?
None
The text was updated successfully, but these errors were encountered: