Re: dropping a column in a production database
From: Frank van Bortel <frank.van.bortel_at_gmail.com>
Date: Wed, 02 Jul 2008 16:00:05 +0200
Message-ID: <31672$486b89e6$524b5c40$13061@cache1.tilbu1.nb.home.nl>
>
> OK, thank you. I was just wondering about unexpected side effects.
>
> Kind regards, Y.
What could be unexpected?
Date: Wed, 02 Jul 2008 16:00:05 +0200
Message-ID: <31672$486b89e6$524b5c40$13061@cache1.tilbu1.nb.home.nl>
yossarian wrote:
> Ed Prochak wrote:
>
>> It is safe in the sense that it will do exactly what you ask. Any data >> in that dropped column will be gone (forever if you do not have it in >> a backup). Note that any applications that used that column will need >> to be rewritten. Packages, functions and procedures dependent on that >> column will become invalid and need to be rewritten. It's all standard >> stuff.
>
> OK, thank you. I was just wondering about unexpected side effects.
>
> Kind regards, Y.
What could be unexpected?
The fact that was part of a key, used for referential integrity of your system?
The fact that is was part of a highly selective index, the sped up the majority of your work by a factor 100?
Nah - can't be - just told you ;)
-- Regards, Frank van BortelReceived on Wed Jul 02 2008 - 09:00:05 CDT