Re: Consequences of adding columns to tables ?

"Spendius" <spendius_at_muchomail.com> wrote:
> Hello,
> What do you think can be the consequences of spending your
> time adding fields to existing tables ?

You could either lose your job, or keep your job. Depending whether that is what you are supposed to be spending your time doing.

> We have several apps here where developers regularly send
> requests to modify tables structures, kind of:
> ALTER TABLE <..> ADD COLUMN X
> UPDATE <..> SET x = '<def. value>'
> ALTER TABLE <..> MODIFY (x DEFAULT VALUE '<def. val.>')
>
> What are the effects in the blocks ? Do records not end up
> having chained/migrated rows all over the place ?

They certainly *could* end up chained/migrated all over the place. Check them out and see.

> What do you think ?

If the alternative is "Let's just make a clob column, then use some kind of psuedo mark-up language to encode the data that belongs in a column of it's own and just stick it in the clob instead, so we don't have to bother the DBA to add a column", then I think adding columns all over the place is a good idea.

Xho

-- 
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service                        $9.95/Month 30GB