-
Notifications
You must be signed in to change notification settings - Fork 22
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
Feature/jld select iri resolution #214
Merged
Merged
Commits on Oct 30, 2022
-
Configuration menu - View commit details
-
Copy full SHA for ba82c01 - Browse repository at this point
Copy the full SHA ba82c01View commit details -
Configuration menu - View commit details
-
Copy full SHA for 002bba0 - Browse repository at this point
Copy the full SHA 002bba0View commit details
Commits on Oct 31, 2022
-
Configuration menu - View commit details
-
Copy full SHA for e1a39c5 - Browse repository at this point
Copy the full SHA e1a39c5View commit details -
There are some js tests that aren't passing, but I want to make the test suite more comprehensive so that we're testing the same thing across platforms and builds. One at a time.
Configuration menu - View commit details
-
Copy full SHA for 3f11f0f - Browse repository at this point
Copy the full SHA 3f11f0fView commit details
Commits on Nov 1, 2022
-
Query vars from .-o flake val also pass datatype, perform IRI resolut…
…ion in results Variables being passed from where statement to where statement always contained only values. For .-o object values, certain downstream processes also need the datatype (e.g. if an IRI, we need to resolve the IRI's value if value is in 'select' statement). Now 'o' values passed through are always two-tuples: [value datatype]. This mean intermediate steps need to know if the value coming through is a two-tuple, so in the query parsing we retain the knowledge of which var is a two-tuple and perform appropriate deconstruction. Also, because mixed-types are allowed, it could be that a object value in one where statement (e.g. ex:friend) might be passed to the subject of the next statement - but if the object value is not an IRI then it will break the following where statement. We now filter for only IRI values in the scenario. Grouping is also an area that requires some additional consideration of the values now being passed in, and that is also adjusted.
Configuration menu - View commit details
-
Copy full SHA for dc07233 - Browse repository at this point
Copy the full SHA dc07233View commit details -
where statement parsed [:vars :all] redundant now with [:vars :all-ty…
…pes] - consolidate
Configuration menu - View commit details
-
Copy full SHA for 151085a - Browse repository at this point
Copy the full SHA 151085aView commit details
Commits on Nov 2, 2022
-
Merge branch 'main' into feature/jld-select-iri-resolution
# Conflicts: # src/fluree/db/query/analytical_parse.cljc # src/fluree/db/query/fql.cljc # test/fluree/db/query/json_ld_compound_test.clj # test/nodejs/flureenjs.test.js
Configuration menu - View commit details
-
Copy full SHA for 0c4c236 - Browse repository at this point
Copy the full SHA 0c4c236View commit details
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.