Hi,

I'm querying the DBpedia SPARQL endpoint using TopBraid Composer. Since the 
amount of data I'm fetching is quite big, I use an offset value to limit the 
output. This works quite well up to an offset value of 9000 in my SPARQL query.

...
ORDER BY ?name
LIMIT 1000
OFFSET 9000

This is the last value where I get any result. When I enter an offset value of 
9001, no triples are fetched anymore. This is quite annoying, for when I don't 
use an offset, TBC/Eclipse collapses under the sheer amount of data that is 
being returned (> 40000).

So my question is: Do you have an internal limit for the offset value 
configured? And if so, is there a workaround available to get queries working 
that include a higher offset value?

Best regards,

Martin




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Dbpedia-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dbpedia-discussion

Reply via email to