| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "PostgreSQL-development Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Arrange for quote_identifier() and pg_dump to not quote keywords |
| Date: | 2007-06-26 15:45:51 |
| Message-ID: | 87myymhg7k.fsf@oxford.xeocode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> Yeah. I'm disinclined to pre-emptively quote things for pie-in-the-sky
> patches. WITH is already a grammar keyword, so it's not a big deal to
> tweak things to quote it, but adding a dozen keywords that have zero
> functionality in the grammar is another thing entirely.
Sure.
> Also, the fact that this particular form of the grammar requires
> reserving the keywords does not prove that there is no way to have the
> features without that. I'd want to see us try a little harder first.
At least some of them are unavoidable conflicts:
select a,b,count(*) from tab GROUP BY cube(a,b)
select a,b,count(*) from tab GROUP BY rollup(a,b)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-26 16:11:28 | Re: [COMMITTERS] pgsql: Arrange for quote_identifier() and pg_dump to not quote keywords |
| Previous Message | Andrew Dunstan | 2007-06-26 15:31:31 | Re: [COMMITTERS] pgsql: Arrange for quote_identifier() and pg_dump to not quote keywords |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-26 15:59:49 | Re: [PATCHES] New Zealand - TZ change |
| Previous Message | Andrew Dunstan | 2007-06-26 15:31:31 | Re: [COMMITTERS] pgsql: Arrange for quote_identifier() and pg_dump to not quote keywords |