FILTER keyword for latest anchor queries#146

Closed

rogerlucena wants to merge 34 commits intogoogle:masterfrom rogerlucena:filter-latest-anchor

+1,857-204

Commits on Sep 30, 2020

Add three new triples to the ?test graph of "planner_test.go" (to better test FILTER)
rogerlucena
committed

Commits on Oct 1, 2020

Add tests for FILTER with latest anchor (in "planner_test.go")
rogerlucena
committed

Commits on Oct 5, 2020

Add tests for FILTER with latest anchor (in "grammar_test.go")
rogerlucena
committed
Add tests for FILTER with latest anchor (in "lexer_test.go")
rogerlucena
committed
Add token type "ItemFilter" to the lexer
rogerlucena
committed
Add token type "ItemFilterFunction" to the lexer
rogerlucena
committed
Add support for FILTER clauses in the grammar
rogerlucena
committed
Add support for FILTER clauses in the lexer
rogerlucena
committed
Add "filters" to the "Statement" type
rogerlucena
committed
Add "filters" to the "queryPlan" type
rogerlucena
committed
Add "workingFilter" to the "Statement" type
rogerlucena
committed
Create FILTER clause hook
rogerlucena
committed
Add String method to FilterClause
rogerlucena
committed
Update String method of queryPlan to show filters as well
rogerlucena
committed
Add FilterOptions to LookupOptions in "storage.go"
rogerlucena
committed
Add support for FILTER clauses in the planner
rogerlucena
committed
Make the volatile driver consume lo.FilterOptions (focusing on latest anchor only for now)
rogerlucena
committed
Update String method of LookupOptions to show FilterOptions as well
rogerlucena
committed
Add tests for FILTER clauses in the semantic.Statement level (in "semantic_test.go")
rogerlucena
committed
Add tests for WhereFilterClauseHook (in "hooks_test.go")
rogerlucena
committed
Minor renaming inside "memory_test.go" to avoid confusion
rogerlucena
committed
Fix problem with partial predicate UUIDs in the volatile driver and make FILTER for latest return multiple triples if they share the same predicate and same latest anchor
rogerlucena
committed
Add tests for the FILTER execution in the volatile driver (in "memory_test.go")
rogerlucena
committed
Allow user to specify for which bindings in the clause each filter can be applied to, improving error checking, and also move verification for supported filter functions to the planner level
rogerlucena
committed
Use a closure to make planner more performant (especially with the addition of multiple filter functions in the future)
rogerlucena
committed
Use an "enum" instead of a "string" for filter operations (less error-prone when implementing the driver)
rogerlucena
committed
Update "memory.go" and "memory_test.go" since filter operations are "enum" now
rogerlucena
committed
Update "hooks_test.go" and "semantic_test.go" since filter operations are "enum" now
rogerlucena
committed
Move "storage.FilteringOptions" to "filter.go" as "filter.StorageOptions"
rogerlucena
committed
Add a String method for filter.StorageOptions
rogerlucena
committed
Use an "enum" instead of a "string" for filter fields (less error-prone when implementing the driver)
rogerlucena
committed
Update "memory.go" and "memory_test.go" since filter fields are "enum" now
rogerlucena
committed
Add an "isEmpty" method for "filter.Operation"
rogerlucena
committed
Update comments for "semantic.FilterClause" and "filter.StorageOptions"
rogerlucena
committed