[
https://issues.apache.org/jira/browse/JENA-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15429482#comment-15429482
]
Andy Seaborne commented on JENA-1225:
-------------------------------------
Looking at TIM and TDB, it seemed to me that pushing the functionality right
back in {{DatasetPrefixStorage}}, the abstraction of prefixes across a stored
dataset, made sense. TDB, for example, does not want get the graph on
{{DatasetGraph.removeGraph}}, it clears the contents at the dataset level so
clearing the prefixes in the same way seemed logical.
And it works for the SPARQL Graph Store Protocol in Fuseki.
> Prefixmappings are not removed permanently from graph with DELETE
> -----------------------------------------------------------------
>
> Key: JENA-1225
> URL: https://issues.apache.org/jira/browse/JENA-1225
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Fuseki 2.4.0
> Environment: Any / appears on Fuseki 2.4.0 or older
> Reporter: Miika Alonen
> Priority: Minor
>
> Prefixmappings are not removed permanently from graphs with DELETE. When
> adding triples to a graph that was deleted earlier old prefixmappings appear
> unexpectedly.
> EXAMPLE:
> PUT http://localhost:3030/example/data?graph=http://example.org/foo#
> @prefix foo: <http://example.org/foo#> .
> foo:foo foo:foo foo:foo
> DELETE http://localhost:3030/example/data?graph=http://example.org/foo#
> PUT http://localhost:3030/example/data?graph=http://example.org/foo#
> @prefix bar: <http://example.org/bar#> .
> bar:bar bar:bar bar:bar .
> GET http://localhost:3030/example/data?graph=http://example.org/foo#
> This returns both old and new prefixmappings:
> @prefix bar: <http://example.org/bar#> .
> @prefix foo: <http://example.org/foo#> .
> bar:bar bar:bar bar:bar .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
