From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Jan Wieck <JanWieck(at)yahoo(dot)com> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, PostgreSQL HACKERS <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PL/pgSQL CURSOR support |
Date: | 2001-05-30 20:09:07 |
Message-ID: | 200105302009.f4UK97N20959@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> DECLARE <name> CURSOR IS <select_stmt> is the Oracle PL/SQL
> syntax. Since PL/pgSQL was written from the start with one
> eye on portability from/to Oracle, I'd like to stick with
> that.
>
> It's relatively simple to just substitute all PLpgSQL (and
> other case combos) occurences by something else, then replace
> the gram.y and scan.l files with whatever you want and voila,
> you come up with another procedural language as compatible as
> possible to your formerly preferred database. There is no
> reason other than that we'll have more PL handlers to
> support, why we shouldn't have two or three different
> procedural SQL dialects. All can coexist and only those used
> in your DB schema will get loaded.
OK, how about this patch that allows both FOR and IS. Seems like a
good idea, and we can document FOR.
Also, I don't see any documentation on the new plpgsql cursor support.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/plain | 1.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2001-05-30 20:09:57 | Re: PL/pgSQL CURSOR support |
Previous Message | Jan Wieck | 2001-05-30 20:00:00 | Re: Support for %TYPE in CREATE FUNCTION |