| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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 20:02:40 |
| Message-ID: | 8445.1471118560@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> writes:
> 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.
Because the SQL standard says so. If we were going to start ignoring
SQL-standard spellings, this area would not be very high on my list,
actually. Their insistence on inventing crazy new special syntaxes
for things that could be normal function calls is what bugs me ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2016-08-13 21:04:01 | Re: condition variables |
| Previous Message | Jim Nasby | 2016-08-13 19:16:03 | Re: Add hint for function named "is" |