Re: [Virtuoso-users] Named Graph Weird Behavior

2012-12-06 Thread Enrico Daga
Hallo, I reply to this thread since my problem is very similar. The list of graphs returned by the simple version of the query is empty, even if there are lots of datasets with rdf:type. I am running VOS Version 06.01.3127. The following workaround seems to skip the bug in the optimizer: SQL> spa

Re: [Virtuoso-users] Named Graph Weird Behavior

2012-03-19 Thread Ivan Mikhailov
Hello Erich, It's due to my dirty hack specifically for select distinct ?g where { graph ?g {?s ?p ?o} } query. It is very popular and it kills the cache of any big database and takes too much time if performed exactly as written. Fortunately, almost all real datasets have at least one rdf:type

[Virtuoso-users] Named Graph Weird Behavior

2012-03-19 Thread Erich Bremer
Hello all, The following SPARQL query using Virtuoso 6.15's sparql end-point returns an empty result set: select distinct ?g where { graph ?g {?s ?p ?o} } However, the following returns the expected results (even if the limit is set to 100 - thinking it was a perceived time-out issue)