Lists: | pgsql-general |
---|
From: | "Robert Fitzpatrick" <robert(at)webtent(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Dropping fields |
Date: | 2003-01-06 20:41:40 |
Message-ID: | 004e01c2b5c4$07837b70$bbc2fea9@COLUMBUS |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-general |
When I drop a field, the field is somewhat left over as
'........pg.dropped.5........', for instance. Is there a command that
needs to be ran after dropping a field?
--
Robert
From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Robert Fitzpatrick" <robert(at)webtent(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Dropping fields |
Date: | 2003-01-06 20:55:53 |
Message-ID: | 1130.1041886553@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-general |
"Robert Fitzpatrick" <robert(at)webtent(dot)com> writes:
> When I drop a field, the field is somewhat left over as
> '........pg.dropped.5........', for instance. Is there a command that
> needs to be ran after dropping a field?
Fix your application to ignore pg_attribute rows where attisdropped
is true.
regards, tom lane
From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Robert Fitzpatrick <robert(at)webtent(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Dropping fields |
Date: | 2003-01-06 20:57:47 |
Message-ID: | 200301062057.h06KvlR11382@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-general |
All applications must now check for dropped columns and not print them.
There is a new pg_attribute.attisdropped for this.
---------------------------------------------------------------------------
Robert Fitzpatrick wrote:
> When I drop a field, the field is somewhat left over as
> '........pg.dropped.5........', for instance. Is there a command that
> needs to be ran after dropping a field?
>
> --
> Robert
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
--
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: | "Robert Fitzpatrick" <robert(at)webtent(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Dropping fields |
Date: | 2003-01-07 00:01:43 |
Message-ID: | 009101c2b5df$f97bf4a0$bbc2fea9@COLUMBUS |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-general |
>
> Fix your application to ignore pg_attribute rows where
> attisdropped is true.
>
So, PostgreSQL 7.3.x now holds all dropped fields information? What is
the purpose?
--
Robert
From: | Doug McNaught <doug(at)mcnaught(dot)org> |
---|---|
To: | "Robert Fitzpatrick" <robert(at)webtent(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Dropping fields |
Date: | 2003-01-07 00:18:32 |
Message-ID: | m3el7phkx3.fsf@varsoon.wireboard.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-general |
"Robert Fitzpatrick" <robert(at)webtent(dot)com> writes:
> >
> > Fix your application to ignore pg_attribute rows where
> > attisdropped is true.
> >
>
> So, PostgreSQL 7.3.x now holds all dropped fields information? What is
> the purpose?
It's the way column dropping is implemented. You couldn't drop
columns at all before 7.3.
-Doug