new rasqal_query_execute2(), old API deprecated #8
Conversation
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
Author
|
Don't accept this pull request yet. More thorough testing found an error. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I have created Data Graphs objects, which as the name suggests contain several graphs.
I recommend to use my new function
rasqal_query_execute2()(with such object as an argument) instead ofrasqal_query_execute()which I deprecated (together with some other functions).The philosophy is to deprecate strong coupling between a query and a dataset and instead use separate "query" and separate "data set" objects. This allows to execute the same query with more than one different dataset. One advantage is that we no more need to recompile a query to use it with a different dataset.