Re: [HACKERS] Happy column dropping

On 23-Jan-00 Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> I wonder if we should throw out a NOTICE when we drop some
>> characteristic of a table?
>
> The problem is mostly that the code doesn't even *know* that it's
> dropping data. If we add code to find the info that's getting lost,
> it's probably little more work to add code to copy it.
>
> I'm of two minds about this. Peter is an energetic new contributor
> and we'd be really foolish to discourage him (I was there not very
> long ago myself). And a limited DROP COLUMN capability is better
> than none at all, so long as its limitations are well-documented.
>
> OTOH, I understand Don Baccus' concern: Postgres is on the cusp of
> being considered professional-grade software --- we are competing
> against multi-K-dollar commercial offerings --- and we jeopardize
> that perception if we add features that are less than fully baked.
> This is definitely in the 50%-baked category...

So why not ./configure --enable-experimental

Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev(at)michvhf(dot)com http://www.pop4.net
128K ISDN: $24.95/mo or less - 56K Dialup: $17.95/mo or less at Pop4
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================