| From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "'jm(dot)poure(at)freesurf(dot)fr'" <jm(dot)poure(at)freesurf(dot)fr>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kovacs Zoltan <kovacsz(at)pc10(dot)radnoti-szeged(dot)sulinet(dot)hu> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: alter table drop column status |
| Date: | 2002-02-13 08:30:37 |
| Message-ID: | FED2B709E3270E4B903EB0175A49BCB104757E@dogbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr]
> Sent: 13 February 2002 08:10
> To: Christopher Kings-Lynne; Hiroshi Inoue; Tom Lane; Kovacs Zoltan
> Cc: pgsql-hackers(at)postgresql(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vaclav Kulakovsky | 2002-02-13 08:47:49 | Postgres 7.2 - Updating rows in cursor problem |
| Previous Message | Andy Latin | 2002-02-13 08:26:24 | Postgre SQL 7.2 QNX6 |