Re: FETCH in subqueries or CTEs - Mailing list pgsql-general

From Pavel Stehule
Subject Re: FETCH in subqueries or CTEs
Date
Msg-id CAFj8pRB3NjnFVk2dD_qSLNzA8AJbCU+E29hbEPStnjyw1WNM_g@mail.gmail.com
Whole thread Raw
In response to FETCH in subqueries or CTEs  (Craig Ringer <ringerc@ringerc.id.au>)
Responses Re: FETCH in subqueries or CTEs  (Craig Ringer <ringerc@ringerc.id.au>)
List pgsql-general
Hello

2012/8/24 Craig Ringer <ringerc@ringerc.id.au>:
> Hi all
>
> I've noticed that FETCH doesn't seem to be supported in subqueries or in
> CTEs.
>
> Is there a specific reason for that, beyond "nobody's needed it and
> implemented it"? I'm not complaining at all, merely curious.
>
> A toy example:
>
>     DECLARE somecursor CURSOR FOR SELECT generate_series(1,1000)
>     SELECT * FROM ( FETCH ALL FROM somecursor ) x;
>
> produces:
>
>     ERROR:  syntax error at or near "FETCH"
>     LINE 1: SELECT * FROM ( FETCH ALL FROM somecursor ) x;
>                         ^
> Same with a CTE:
>
>      WITH x AS ( FETCH ALL FROM somecursor ) SELECT * FROM x;
>
> ERROR:  syntax error at or near "FETCH"
> LINE 1: WITH x AS ( FETCH ALL FROM somecursor ) SELECT * FROM x;
>

you can't mix planned and unplanned statements together - think about
stored plans every time

Regards

Pavel

> --
> Craig Ringer
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general


pgsql-general by date:

Previous
From: Sébastien Lorion
Date:
Subject: Re: Amazon High I/O instances
Next
From: Jason Dusek
Date:
Subject: Re: Rules, Windows and ORDER BY