| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Greg Stark <stark(at)mit(dot)edu>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add hint for function named "is" |
| Date: | 2016-08-13 19:16:03 |
| Message-ID: | 4d1b7785-5c64-13a1-74ac-d0708044b08f@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/12/16 1:40 PM, Tom Lane wrote:
> What this is telling us is that given input like, say,
>
> SELECT 'foo'::character varying
>
> Bison is no longer sure whether "varying" is meant as a type name modifier
> or a ColLabel. And indeed there is *no* principled answer to that that
> doesn't involve giving up the ability for "varying" to be a ColLabel.
> Just promoting it to a fully reserved word (which it is not today)
> wouldn't be enough, because right now even fully reserved words can be
> ColLabels.
FWIW, I've always disliked how some types could contains spaces without
being quoted. AFAIK nothing else in the system allows that, and I don't
see why character varying and timestamp with* should get a special pass.
I doubt we could get rid of this in CREATE TABLE, but I wonder how many
people actually cast using the unquoted form.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-08-13 20:02:40 | Re: Add hint for function named "is" |
| Previous Message | Vladimir Sitnikov | 2016-08-13 18:32:53 | Re: Slowness of extended protocol |