| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pl/pgsql: END verbosity |
| Date: | 2005-06-26 15:24:54 |
| Message-ID: | 42BEC8C6.8020407@samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Peter Eisentraut wrote:
> It is required by the SQL standard.
No, it isn't -- PL/PgSQL is not defined by the SQL standard. I guess
you're referring to SQL/PSM, but that has only a passing resemblance to
PL/PgSQL. Implementing SQL/PSM in some form would definitely be worth
doing (especially now that MySQL have), but I haven't seen any plans to
do that by adapting PL/PgSQL to SQL/PSM.
In any case, there are plenty of cases in which we accept a superset of
the syntax defined by the SQL standard -- DROP TABLE { RESTRICT |
CASCADE }, for example. We have never interpreted compliance with the
SQL specification to mean that we must *only* accept the standard's
syntax and nothing else.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-06-26 15:57:57 | Re: pl/pgsql: END verbosity |
| Previous Message | Atsushi Ogawa | 2005-06-26 14:30:52 | Re: [PATCHES] regexp_replace |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2005-06-26 15:57:57 | Re: pl/pgsql: END verbosity |
| Previous Message | Atsushi Ogawa | 2005-06-26 14:30:52 | Re: [PATCHES] regexp_replace |