Re: is syntax columname(tablename) necessary still?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:12:48
Message-ID: AANLkTinh=9oscJME2Rgy_bp4U_UKKhW1p9A-Pn=K8kSE@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 9, 2010 at 11:06 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> 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 ( ...

They name to be type_func_keywords, perhaps, but not fully reserved.
And they'd still need that treatment anyway. Even if cube(whatever)
can't mean "extract a column called cube from table whatever", it can
still mean "call a function called cube on a column called whatever".

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-08-09 15:16:47 Re: regclass, \d command and temp tables
Previous Message Robert Haas 2010-08-09 15:11:04 Re: dynamically allocating chunks from shared memory