Can't delete triples with typed literals in VOS 7.1

[j2blake]

Hi;

I am unable to delete a triple whose object is a typed literal. I can use the following SPARQL queries in iSQL to demonstrate the problem.

I create the triple,

SPARQL 
INSERT IN GRAPH <http://mine> { 
    <http://mine#s> <http://mine#p> "Estimated"^^<http://www.w3.org/2001/XMLSchema#string> 
};

I attempt to delete it,

SPARQL 
WITH GRAPH <http://mine> 
DELETE { 
    <http://mine#s> <http://mine#p> "Estimated"^^<http://www.w3.org/2001/XMLSchema#string> 
} WHERE { 
    <http://mine#s> <http://mine#p> "Estimated"^^<http://www.w3.org/2001/XMLSchema#string> 
} ;

but it's still there:

SPARQL 
SELECT * 
WHERE { 
    GRAPH <http://mine> { 
        ?s ?p ?o 
    } 
} ;

This is similar to issue #247, which has been resolved. Thanks to that fix, I can delete the triple like this:

SPARQL 
WITH GRAPH <http://mine> 
DELETE { 
    <http://mine#s> <http://mine#p> ?o 
} WHERE { 
    <http://mine#s> <http://mine#p> ?o 
} ;

but this will delete any other triples that have the same subject and predicate -- triples that I want to keep.

This also seems similar to issue #198 but is apparently different enough that it is still a problem.

Any thoughts?

Jim

[HughWilliams]

@j2blake: You indicate Virtuoso 7.1 is being used is that correct ? And if so I suggest updating to the latest 7.2 stable or develop branches are there have been many fixes some of which for the deletion of graphs/triples ...

[j2blake]

Thank you, Hugh. That is correct. I will try the latest version.

[athalhammer]

Hi,

I can confirm this behavior with version 7.2 (Version 07.20.3214-pthreads for Linux as of Jul 14 2015)

s is a blank node. Everything that matches but typed literals is deleted from the default graph with the following command:

set.asDatasetGraph().getGraph(NodeFactory.
createURI("urn:x-arq:DefaultGraphNode")).remove(s,Node.ANY, Node.ANY);

In fact, the Java program gets stuck there.

[HughWilliams]

@athalhammer: There have been number for updates to the blank node handling it the Virtuoso Jena & Sesame provide over the past few months, thus I would suggest update your build from 14th Jul to the latest git develop/7 which would contain all these fixes, to see if the problem persists ...