Re: Using Packages makes ALTER TABLE dangerous

From: Joachim Zobel <jzobel_at_my-dejanews.com>
Date: Wed, 10 Dec 2003 23:26:51 +0100
Message-ID: <pan.2003.12.10.22.26.46.78270@my-dejanews.com>

On Wed, 10 Dec 2003 22:52:07 +0100, Frank wrote:

>>>And when using encapsulation, how can you alter the table? Surely this
>>>should be solved withing the package...

>>
>>
>> Huh?
>>
>> If you go from
>>
>> class foo {
>> public:
>> foo() {
>> }
>> private:
>> int bar;
>> }
>>
>> to
>>
>> class foo {
>> public:
>> foo() {
>> bar = 0;
>> }
>> private:
>> int bar;
>> }
>>
>> there should be an interface?!

> 
> I fail to see what this has to do with PL/SQL and
> Oracle tables being dropped and recreated

I just wanted to demonstrate that an ALTER TABLE foo MODIFY(bar INTEGER DEFAULT 0) is a source code change and therefore nothing that can or should be encapsulated.

Joachim

-- 
Warnung: \" kann Augenkrebs verursachen. 

Received on Wed Dec 10 2003 - 16:26:51 CST