W3C home > Mailing lists > Public > public-sparql-dev@w3.org > April to June 2009

Re: LIMIT problem (Paging)

From: Mirko <idonthaveenoughinformation@googlemail.com>
Date: Thu, 28 May 2009 12:22:59 +0200
Message-Id: <BF572483-4E1A-4BAF-A927-DE43B2DC9BED@googlemail.com>
To: public-sparql-dev@w3.org, Richard Newman <rnewman@franz.com>
first thank you all for your tips. well, you convinced me that paging  
with limit/offset and orderby , as recommended in the spec, is not  
really a good idea (with larger datasets). What's really the problem  
here is the ordering.

> If a store has an index on my:hasUserID (and that index happens to  
> be in SPARQL's defined order!) then results can be generated in  
> ordered sequence.

Do you mean, I can assume to get "ordered" results without explicit  
"ORDER BY" in the query, given the appropriate index? independent from  
the database implementation? In my current setting (Sesame with  
NativeStore - default index spoc, posc) this is not the case.

Thanks, Mirko
Received on Thursday, 28 May 2009 11:42:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:15:50 UTC