Re: is syntax columname(tablename) necessary still?

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: is syntax columname(tablename) necessary still?
Date: 2010-08-09 15:06:19
Message-ID: AANLkTi=buBSW9F3PwEYBpsDzcFSCd_vsLupAXkmBq8f8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2010/8/9 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Greg Stark <gsstark(at)mit(dot)edu> writes:
>> Personally I think cube is uncommonly used and CUBE an important
>> enough SQL feature that we should just bite the bullet and kill/rename
>> the contrib module.
>
> Yeah.  It looks to me like CUBE will have to be a type_function_name
> keyword (but hopefully not fully reserved), which will mean that we
> can't have a contrib module defining a type by that name.  Ergo, rename.

I am afraid, CUBE and ROLLUP have to be a reserved keyword because as
type_function_name is in conflict with func_name ( ...

Regards

Pavel Stehule

>
>> ... Now conceivably it's a word users
>> might be using in their schema and that might be a good enough reason
>> to hack up the grammar -- but it's not like it's a new keyword in SQL
>> so it shouldn't come as a surprise to users when they get an error.
>
> As long as we can avoid making it fully reserved, tables/columns named
> "cube" will still work, so the damage should be limited.
>
>                        regards, tom lane
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2010-08-09 15:10:14 regclass, \d command and temp tables
Previous Message Bruce Momjian 2010-08-09 15:02:07 Re: dynamically allocating chunks from shared memory