| From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
|---|---|
| To: | Michael Meskes <meskes(at)topsystem(dot)de> |
| Cc: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>, PostgreSQL Hacker <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] ecpg stuff |
| Date: | 1998-02-18 08:55:40 |
| Message-ID: | 34EAA20C.47BCC7DB@sable.krasnoyarsk.su |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeroen van Vianen | 1998-02-18 08:57:21 | Bug in evaluation of AND |
| Previous Message | Meskes, Michael | 1998-02-18 08:52:52 | RE: [HACKERS] ecpg stuff |