| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Larry Rosenman <ler(at)lerctr(dot)org> |
| Cc: | 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:18:10 |
| Message-ID: | 200301272118.h0RLIA407117@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Of course we are not going to default this to ON.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-01-27 21:19:35 | Re: Request for qualified column names |
| Previous Message | Tom Lane | 2003-01-27 21:14:52 | Re: Request for qualified column names |