You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The actual context is propagated through HTTP query param default-graph-uri which is equivalent to FROM in SPARQL query. As I understand, according to SPARQL standard if FROM is specified, but FROM NAMED is not, then there will be no graphs to match with GRAPH:
Each FROM clause contains an IRI that indicates a graph to be used to form the default graph. This does not put the graph in as a named graph.
Or probably it makes sense to use different base queries. The existing query works fine when contexts are not provided. When contexts are specified, something like SELECT * WHERE { GRAPH ?ctx { ?s ?p ?o }} together with named-graph-uri would be more correct.
Expected Behavior
Steps To Reproduce
No response
Version
5.1.0
Are you interested in contributing a solution yourself?
None
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Current Behavior
When getting all statements from a given graph with
connection.getStatemnts(null, null, null, ctx)
forSPARQLConnection
, it uses the following query:The actual context is propagated through HTTP query param
default-graph-uri
which is equivalent toFROM
in SPARQL query. As I understand, according to SPARQL standard ifFROM
is specified, butFROM NAMED
is not, then there will be no graphs to match withGRAPH
:As a result projected
?ctx
is always empty.I guess in addition to setting
default-graph-uri
setBindings
should also setnamed-graph-uri
. See https://github.com/eclipse-rdf4j/rdf4j/blob/main/core/repository/sparql/src/main/java/org/eclipse/rdf4j/repository/sparql/SPARQLConnection.java#L786Or probably it makes sense to use different base queries. The existing query works fine when contexts are not provided. When contexts are specified, something like
SELECT * WHERE { GRAPH ?ctx { ?s ?p ?o }}
together withnamed-graph-uri
would be more correct.Expected Behavior
Steps To Reproduce
No response
Version
5.1.0
Are you interested in contributing a solution yourself?
None
Anything else?
No response
The text was updated successfully, but these errors were encountered: