Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
Jena 4.3.2
-
None
-
None
-
None
Description
Summary: I think this boils down to DynamicDatasetGraph in DynamicDatasets: the provided baseDSG is never used except for cloning the context. The private function getProjected is never used anywhere, see
The problem occurs when we call a SPARQL UPDATE with using-graph-uri which we map to UpdateWithUsing.addUsing. On execution of such an update, this triggers a code path that goes through DynamicDatasets.dynamicDataset. The result is that the WHERE clause of an UPDATE only gets to see the default graph, but none of the other named graphs in the original dataset. Then, the GRAPH <...> clause does not work correctly.
My understanding of the USING/using-graph-uri contract is that this only sets the default graph yet all other graphs in the dataset remain visible. Is this not the case?