Re: alter table drop column status - Mailing list pgsql-hackers

From Dave Page
Subject Re: alter table drop column status
Date
Msg-id FED2B709E3270E4B903EB0175A49BCB104757E@dogbert.vale-housing.co.uk
Whole thread Raw
In response to alter table drop column status  (Kovacs Zoltan <kovacsz@pc10.radnoti-szeged.sulinet.hu>)
List pgsql-hackers

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm.poure@freesurf.fr] 
> Sent: 13 February 2002 08:10
> To: Christopher Kings-Lynne; Hiroshi Inoue; Tom Lane; Kovacs Zoltan
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] alter table drop column status
> 
> 
> Le Mercredi 13 Février 2002 06:14, Christopher Kings-Lynne a écrit :
> > This seems fantastic - why can't this be committed?  Surely if it's 
> > committed then the flaws will fairly quickly be ironed out? 
>  Even if 
> > it has flaws, then if we say 'this function is not yet stable' at 
> > least people can start testing it and reporting the problems?
> 
> +1. What are the reasons why this hack was not applied?

See /doc/TODO.detail/drop in the source tree. That pretty much explains it.

Regards, Dave.


pgsql-hackers by date:

Previous
From: Jean-Michel POURE
Date:
Subject: Re: alter table drop column status
Next
From: Hiroshi Inoue
Date:
Subject: Re: alter table drop column status