Jan has approved the following patch that allows both FOR and IS for
> > 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
In response to
pgsql-hackers by date
|Next:||From: Lamar Owen||Date: 2001-05-31 17:18:32|
|Subject: Re: Non-ASCII locales (was:Re: Imperfect solutions)|
|Previous:||From: Bruce Momjian||Date: 2001-05-31 17:00:03|
|Subject: Re: Access statistics|