Re: cursors on prepared queries

From: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
To: "Andro" <andromede(at)gmail(dot)com>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: cursors on prepared queries
Date: 2006-09-12 10:47:45
Message-ID: 24793.125.24.222.234.1158058065.squirrel@webmail.xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-interfaces

On Tue, September 12, 2006 17:18, Andro wrote:

> PREPARE plan_name(int) AS SELECT * FROM abc WHERE a = $1;
> DECLARE cur CURSOR FOR EXECUTE(3);

(You'd probably also want to mention the name of the prepared statement
that you're executing somewhere :)

> Is something wrong or is it just not supported by postgres?
> Manual talks about read only cursors but I didn't find out discussions
> about
> "anti-prepared-statement-cursors".

Well, the documentation for DECLARE says that the query that cursor
executes must be a "SELECT command"--not that I personally know the
reasons behind it:

http://www.postgresql.org/docs/8.1/interactive/sql-declare.html

Jeroen

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Andro 2006-09-12 12:34:53 Re: cursors on prepared queries
Previous Message Andro 2006-09-12 10:18:39 cursors on prepared queries