Stardog response to exportDB with nonexistent graphURI not helpful

[jrh...@thematix.com]

Running Stardog 3.1.2 using stardog.js 0.3.0  in node.

When I execute exportDB with a graphUri option and the named graph does not exist, I get back a dump of the entire database.

I need to return a 404 not found to the browser in this case, but no simple way to tell the difference between entire database export and named graph export.

Better would be if the option is not tag:stardog:api:context:all and the named graph is not found, return a zero length string.

[Michael Grove]

Can you provide a code example of where this occurs?  I am not able to reproduce this behavior on the command line:

```

mhgrove:dist mhgrove$ ./bin/stardog data export --named-graph urn:doesNotExist --format TRIG foo

@prefix owl: <http://www.w3.org/2002/07/owl#> .

@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .

@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

@prefix stardog: <tag:stardog:api:> .

@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

```

Cheers,

Mike

 

--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
stardog+u...@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en