Re: Request for qualified column names - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: Request for qualified column names
Date
Msg-id 1043702455.68971.57.camel@jester
Whole thread Raw
In response to Re: Request for qualified column names  (Larry Rosenman <ler@lerctr.org>)
List pgsql-hackers
On Mon, 2003-01-27 at 15:50, Larry Rosenman wrote:
> --On Monday, January 27, 2003 15:49:06 -0500 Bruce Momjian
> <pgman@candle.pha.pa.us> wrote:
>
> >
> > My idea on this after chat with Dave was to add a GUC option that puts
> > the schema.table.column name as the default column label, rather than
> > just the column name.  (That's so easy, I think even I could do it.)  If
> > they over-ride it with AS, or if it is an aggregate or FROM subquery, we
> > just return the default label as we do now --- we could return no label
> > for those cases, but that seems too drastic.  I am not overly excited
> > about doing this at the protocol level unless there is major need for it.
> DONT DEFAULT TO THE NEW ONE WITHOUT NOTICE!
>
> You will ***BREAK*** people.

Agreed.  This is the way we probably want to go -- but we'll need a guc
for a release or 2 -- One release with default as current, one with
default as new way, 7.6 can remove Guc.

--
Rod Taylor <rbt@rbt.ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Request for qualified column names
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] New hashed IN code ignores distinctiveness of subquery