From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Hannu Krosing <hannu(at)tm(dot)ee> |
Cc: | The Hermit Hacker <scrappy(at)hub(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Well, then you keep your darn columns |
Date: | 2000-01-24 22:34:33 |
Message-ID: | 200001242234.RAA02667@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > Can you
> > imagine having all those user apps tha query pg_attribute supress that
> > column. Sound like too much work to me.
>
> To me it sounds like a thing that _must_ be done at major number change,
> so 7.0 is a good place.
>
> OTOH, we could provide SQL92 ways for getting the info that current user
> apps get by querying pg_attribute.
>
> IIRC it requires a bunch of views on system tables, some of which could be
> lifted straight from psql's \d* commands.
If this is going to require any significant backend baggage, I say drop
it. Things are complicated enough. I did temp tables in one file so we
would not have "I am a temp" and "I am not a temp" floating all over the
backend. I don't really want "I am not an attribute" around either.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-01-24 22:43:41 | Re: [HACKERS] Happy column dropping |
Previous Message | Don Baccus | 2000-01-24 22:30:19 | Re: [HACKERS] Well, then you keep your darn columns |