Or we should change the declare/open behaviour in that it ignores the
embedded SQL declare command and just sends the declare command when it
finds an open. But then standard may say that the actual way is correct.
Michael
--
Dr. Michael Meskes, Project-Manager | topsystem Systemhaus GmbH
meskes@topsystem.de | Europark A2, Adenauerstr. 20
meskes@debian.org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10
> -----Original Message-----
> From: Vadim B. Mikheev [SMTP:vadim@sable.krasnoyarsk.su]
> Sent: Wednesday, February 18, 1998 9:56 AM
> To: Michael Meskes
> Cc: Thomas G. Lockhart; PostgreSQL Hacker
> Subject: Re: [HACKERS] ecpg stuff
>
> Michael Meskes wrote:
> >
> > - and check resp. tell me whether the cursor behaviour is correct.
> Currently
> > the declare statement is send to the backend via PQexec. The open
> statement
> > is ignored and the fetch is executed as fetch via PQexec. I think
> the data
> > shouldn't be processed before the cursor is opened. But I do not
> know
> > what PostgreSQL does with the declare command.
>
> DECLARE: parser + optimizer + ExecutorStart (initializes plan nodes:
> checks permissions, opens tables & indices).
> Is OPEN statement in standard ?
> If yes then we could call ExecutorStart() for the OPEN someday.
>
> Vadim