From: | Rod Taylor <rbt(at)rbt(dot)ca> |
---|---|
To: | Larry Rosenman <ler(at)lerctr(dot)org> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Reggie Burnett <rykr(at)bellsouth(dot)net>, "'Dave Cramer'" <dave(at)fastcrypt(dot)com>, "'PostgreSQL Hackers Mailing List'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Request for qualified column names |
Date: | 2003-01-27 21:20:56 |
Message-ID: | 1043702455.68971.57.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)candle(dot)pha(dot)pa(dot)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(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-01-27 21:29:52 | Re: [BUGS] New hashed IN code ignores distinctiveness of subquery |
Previous Message | Bruce Momjian | 2003-01-27 21:19:35 | Re: Request for qualified column names |