Re: [Virtuoso-users] Blank nodes in INSERT DATA

On Jan 2, 2013, at 12:14 PM, Rob Vesse wrote: > The difference in behavior is in line with the SPARQL specification > > An INSERT DATA clause can only add concrete triples I.e. no blank nodes are > permitted Use of blank nodes is just fine in concrete triples (what the SPARQL 1.1 grammar calls

Re: [Virtuoso-users] Wrong graph URI

On Dec 12, 2012, at 7:24 AM, Kingsley Idehen wrote: > The problem is that these graphs are purpose specific. For instance, they > don't have anything to do with DBpedia, they are installed by for use by our > Faceted Browser (re. ). Basically, this is where it gets confusing > since we have two

Re: [Virtuoso-users] dump_graphs() error

On Aug 23, 2011, at 4:05 PM, Mitko Iliev wrote: > Hi Greg, > > Please enable the CallstackOnException = 1 in the virtuoso.ini [Parameters] > section , then execute the dump_graphs () and send me the call-stack included > in the error string. Hi Mitko, Perhaps this isn't bad data but a heisenb

Re: [Virtuoso-users] dump_graphs() error

On Aug 23, 2011, at 3:49 AM, Mitko Iliev wrote: > Hi Greg, > > Please make sure the 'env' variable in dump_one_graph procedure is > initialized as : > env := vector (dict_new (16000), 0, '', '', '', 0, 0, 0, 0); > Also you can take the procedure from attached script. Hi Mitko, After recoveri

Re: [Virtuoso-users] dump_graphs() error

On Aug 22, 2011, at 8:58 PM, Hugh Williams wrote: > Hi Greg, > > Was the data reloaded using this updated 6.1.3 binary or was the existing > database file used ie that was loaded with the 6.1.2 binary ? As I would > suggest reloading the data into a new empty database using the 6.1.3 binary, >

Re: [Virtuoso-users] dump_graphs() error

On Aug 21, 2011, at 8:46 AM, Hugh Williams wrote: > Looking at the version 6.1.2 you report as being used and based on Ivan's > (who wrote these procedures) comment I would suggest you database be upgraded > to the latest 6.1.3 release to use these procedures. The latest 6.1.3 > snapshot can be

Re: [Virtuoso-users] dump_graphs() error

Hugh, Thanks for the response. On Aug 20, 2011, at 8:02 PM, Hugh Williams wrote: > The error implies that there is a bad triple in one of the graphs being > dumped, can you please check the “virtuoso.log” file to see if any errors are > reported there. The Virtuoso trace_on() function can als

[Virtuoso-users] dump_graphs() error

I've been trying to use the dump_graphs() function from to dump the RDF contents of my virtuoso database, and I've been getting the following error: [willig4@sam db]$ cat /tmp/dump.txt dump_graphs('/tmp/dump', 1); [willig4

[Virtuoso-users] transaction support in isql for multiple sparql opeations?

hat is the case, should I expect the RDF loading functions (e.g. RDF_LOAD_RDFXML_MT and TTLP_MT) to work the same as the sparql commands (CLEAR/LOAD GRAPH) used in the example above? thanks, gregory williams

[Virtuoso-users] virtuoso sparql optional+filter bug?

I've run into what I believe is another bug in virtuoso's SPARQL implementation. Unless you've got some perverse RDF loaded into the database, this following query shouldn't return any variable bindings: SELECT * WHERE { OPTIONAL { [] ?f . FILTER(

[Virtuoso-users] SPARQL OPTIONAL/FILTER issues with Virtuoso

I'm running into what seems like a bug in virtuoso's SPARQL optimizer. I'm trying to execute a query using the OPTIONAL/!BOUND trick for negation and getting this error message: Internal error: sparp_gp_detach_all_filters(): optimization tries to break the semantics of LEFT OUTER JOIN for OPTIO

[Virtuoso-users] Bad SPARQL results from DBPedia endpoint?

ut it struck me as odd. Is this the expected behavior of DESCRIBE in Virtuoso? Is the algorithm used for DESCRIBE described anywhere? thanks, gregory williams [1] http://dbpedia.org/sparql?default-graph-uri=&query=select+*+where+%7B+%3Fs+a+%3Fo+%7D

[Virtuoso-users] http accept header problems on dbpedia endpoint?

first returns 200 OK, while the second returns 406 Unacceptable. The only difference is "text/x-turtle" versus "text/turtle". Any thoughts as to why this might be happening? thanks, gregory williams