[dotNetRDF-bugs] Scope of autassigned bland node IDs

[Tomek P. <to...@pl...>]

Hi Rob

I have just updated to latest dotNetRDF available on NuGet and I'm
experiencing two issues.

1. In my unit tests I relied on the way the library assigns blank node
identifiers: autos1, autos2 and so on. When I run the tests separately
each one passes but when I batch them they fail because in subsequent
tests blank nodes are name autos2, autos3, etc. However they don't
share the same graph or triple store. Have you changed this behavior
delbierately?

2. There is a bad memory leak in during SPARQL execution of this:

PREFIX rr: <http://www.w3.org/ns/r2rml#>
DELETE { ?map rr:graph ?value . }
INSERT { ?map rr:graphMap [ rr:constant ?value ] . }
WHERE { ?map rr:graph ?value } ;

DELETE { ?map rr:object ?value . }
INSERT { ?map rr:objectMap [ rr:constant ?value ] . }
WHERE { ?map rr:object ?value } ;

DELETE { ?map rr:predicate ?value . }
INSERT { ?map rr:predicateMap [ rr:constant ?value ] . }
WHERE { ?map rr:predicate ?value } ;

DELETE { ?map rr:subject ?value . }
INSERT { ?map rr:subjectMap [ rr:constant ?value ] . }
WHERE { ?map rr:subject ?value }

The full code is simply:

var dataset = new InMemoryDataset(store, R2RMLMappings.BaseUri);
            ISparqlUpdateProcessor processor = new
LeviathanUpdateProcessor(dataset);
            var updateParser = new SparqlUpdateParser();

            processor.ProcessCommandSet(updateParser.ParseFromString(ShortcutSubmapsReplaceSparql));

Is this a know problem and has been already fixed or should I
investigate closely?

Thanks,
Tom