W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > April to June 2005

Re: OFFSET/LIMIT, cursors, and DAWG scope boundaries

From: Steve Harris <S.W.Harris@ecs.soton.ac.uk>
Date: Wed, 6 Apr 2005 17:17:44 +0100
To: "'RDF Data Access Working Group '" <public-rdf-dawg@w3.org>
Message-ID: <20050406161744.GH9626@login.ecs.soton.ac.uk>

On Wed, Apr 06, 2005 at 03:19:58 +0100, Dave Beckett wrote:
> 
> On Wed, 6 Apr 2005 08:50:23 -0400, Bijan Parsia <bparsia@isr.umd.edu> wrote:
> 
> Just answering one thing:
> 
> > Limit is the "relative" end point. Offset is the actual start point. 
> > (Hmm. I didn't see any statement forbidding the offset > limit. That 
> > just returns 0 results?) Both are one shot deals (i.e., they are done 
> > once in the context of a query).
> 
> In the current design, the order of the controls is (rq23, sec 10.1)
>   1. projection 2. distinct 3. order by 4. limit 5. offset
> (although there are some severe wording problems there that I'll write down
> in my review)
> 
> so limit is an absolute number, it counts all solutions, and does not start
> counting relative to a particular offset.
> 
> offset applies last and picks the start point from the resulting sequence
> after steps 1. to 4.

OK, well thats not what MySQL for one does, it applies offset then limit.
That seems less supprising to me.

- Steve
Received on Wednesday, 6 April 2005 16:17:52 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:15:23 GMT