| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: minor patch submission: CREATE CAST ... AS EXPLICIT |
| Date: | 2011-05-24 21:13:11 |
| Message-ID: | 15708.1306271591@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On lr, 2011-05-21 at 15:46 +0200, Fabien COELHO wrote:
>> From a language definition perspective, it is helpful to have a name for
>> every case instead of an implicit fallback, without any word to describe
>> it. See for instance "CREATE USER CREATEDB/NOCREATEDB" or "CREATE RULE ...
>> DO ALSO/INSTEAD" for similar occurences of naming default cases.
> Oddly enough, we did add the DO ALSO syntax much later, and no one
> complained about that, as far as I recall.
Sure, but CREATE RULE is entirely locally-grown syntax, so there is no
argument from standards compliance to consider there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-05-24 21:35:24 | Re: about EDITOR_LINENUMBER_SWITCH |
| Previous Message | Tom Lane | 2011-05-24 21:11:17 | Re: about EDITOR_LINENUMBER_SWITCH |