On Tue, 2008-03-25 at 11:47 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Tue, 2008-03-25 at 10:45 -0400, Bruce Momjian wrote:
> >> Where does this FETCH appear in a SELECT?
>
> > It's supposed to go *after* the OFFSET clause in a query, but making it
> > a simple synonym
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Tue, 2008-03-25 at 10:45 -0400, Bruce Momjian wrote:
>> Where does this FETCH appear in a SELECT?
> It's supposed to go *after* the OFFSET clause in a query, but making it
> a simple synonym for LIMIT seems most sensible.
Huh? OFFSET isn't in standard
On Tue, 2008-03-25 at 10:45 -0400, Bruce Momjian wrote:
> Simon Riggs wrote:
> > SQL200n specifies a new command similar to our LIMIT
> >
> > FETCH { FIRST | NEXT } n { ROW | ROWS } ONLY
> >
> > and also that the OFFSET command can have an optional suffix
> >
> > { ROW | ROWS }
> >
> > Seems li
Simon Riggs wrote:
> SQL200n specifies a new command similar to our LIMIT
>
> FETCH { FIRST | NEXT } n { ROW | ROWS } ONLY
>
> and also that the OFFSET command can have an optional suffix
>
> { ROW | ROWS }
>
> Seems like a % project for the TODO list
Where does this FETCH appear in a SELECT?
SQL200n specifies a new command similar to our LIMIT
FETCH { FIRST | NEXT } n { ROW | ROWS } ONLY
and also that the OFFSET command can have an optional suffix
{ ROW | ROWS }
Seems like a % project for the TODO list
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
PostgreSQL UK 2
