Re: Using Packages makes ALTER TABLE dangerous

From: Joachim Zobel <jzobel_at_my-dejanews.com>
Date: Tue, 09 Dec 2003 18:05:36 +0100
Message-ID: <pan.2003.12.09.07.26.30.738382@my-dejanews.com>

On Mon, 08 Dec 2003 21:03:12 -0600, Galen Boyer wrote:

> On Mon, 08 Dec 2003, jzobel_at_my-dejanews.com wrote:

>> 
>> Is there a way to use packages for table encapsulation and
>> still be able to do ALTER TABLEs without fear?

>
> When a change is needed to your application's codebase, do you
> actually just recompile a single class and deploy it, or do you
> recompile your entire application and redeploy that? After
> answering that, don't you think that the flexibility you get with
> the database's engine is actually quite good?

It differs. On a mod_perl Apache I can hot deploy interface compatible changes into the running system. On a legacy SSJS system I have to compile every HTML change and restart an application that thereby looses its in memory state. So Oracles flexibility is intermediate.

> Maybe, instead of getting all pissed cause you had a little bit of
> trouble, you just need to figure out how to find what breaks and make
> sure you recompile those things? Oracle gives you lots of solid tools
> and lots of documentation on how to do this. Far more than some java
> environment does.

Those things could not be recompiled, because a broken application error handling had left behind idle active connections. The point is: If the package can not be compiled, it would be nice if the dependency checker would stop me from invalidating it.

Why do you think I have to use Java? I don't :-)

Sincerely,
Joachim

-- 
Warnung: \" kann Augenkrebs verursachen. 

Received on Tue Dec 09 2003 - 11:05:36 CST