Enhancement#425 entity graph fetch#433
Merged
Merged
Conversation
Signed-off-by: Martin Ledvinka <martin.ledvinka@hotmail.com>
Signed-off-by: Martin Ledvinka <martin.ledvinka@hotmail.com>
…to the end. Performance - SPARQL engines work better with OPTIONAL at the end of BGP.
…o query via a hint.
…om query result.
In preparation for supporting loading of an entity graph based on fetch graph.
…g axioms in OOMapper.
Populate load state descriptor based on fetch graph config.
…ed instance loading. Load state of non-entity fields not specified by fetch graph is unknown, entity fields are not loaded.
…om SparqlAssemblyModifier. Use Visitor pattern to allow concrete implementations without tight coupling.
…entity loading optimized queries.
…no Types field. Order query results to get stable row ordering, fix issues.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves #425 by introducing support for fetch graphs.