| From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
|---|---|
| To: | "Meskes, Michael" <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 09:28:31 |
| Message-ID: | 34EAA9BF.3FF4F672@sable.krasnoyarsk.su |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Meskes, Michael wrote:
>
> 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.
It seems that OPEN is in standard and this is really bad that we havn't
OPEN statement: using DECLARE we could plan query once and then
re-use this plan many times - OPEN, FETCH-es, CLOSE; OPEN, ...
Also, we could use queries with parameters (like in SQL-funcs: $1, ...)
in DECLARE and then assign parameter' values in OPEN and execute
cursor for different values.
Isn't this what Oracle allow ?
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vadim B. Mikheev | 1998-02-18 10:53:11 | Re: [HACKERS] Bug in evaluation of AND |
| Previous Message | Jeroen van Vianen | 1998-02-18 08:57:21 | Bug in evaluation of AND |