-
Notifications
You must be signed in to change notification settings - Fork 544
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
Bug when using FROM statements #2670
Comments
related discussion #2591 |
I believe I've identified part of the problem. In evaluate.py, the
Replacing |
I made a fix here for another issue. But it seems that it also fixes yours. Could you confirm?
Since you define your dataset explicitly with |
@apicouSP Your fix is excellent, thanks for putting that together. I can't see any issues with your solution, hopefully it can be merged into the next release. |
Using a FROM statement to query a Dataset induces a number of problems. Consider the following example:
This snippet loads two named graphs, each with a single triple, then queries
ex:Graph1
.After this query, the graph now contains a duplicate of
ex:Graph1
in the default graph:Aside from inadvertently increasing the size of the Dataset, this also induces a bug when querying other graphs in the Dataset. For example, if we now query
ex:Graph2
, we find that we get an erroneous result:I have no clue as to the cause of this behaviour, but clearly something is wrong with the handling of FROM statements. Furthermore, none of the queries show here work if
sparql.SPARQL_DEFAULT_GRAPH_UNION = True
, which appears to be a separate but related problem.The text was updated successfully, but these errors were encountered: