Re: how to alter table columns:

>>What do you think about updateing sys.col$ ?
>
>I think it is a hugely *BAD* terrible idea. Words cannot describe how bad
it
>could be.
>you have procedures that should be invalid (but aren't) out there. they
could
>and will raise internal errors (these procedures that reference this old
column
>*should* work but they won't and the system won't understand why)
>you have views that should be invalid (but aren't) out there.... same as
above.
>I see lots of internal errors in your future.
>you have constraints that reference this now non-existent column. they can
and
>will raise internal errors.
>don't even want to think what this would do to replication.
>who knows what hidden side effects may occur. I know of real side effects,
some
>above, but that is not an inclusive list.

>Thomas Kyte tkyte_at_us.oracle.com
>Oracle Service Industries Reston, VA USA
>Opinions are mine and do not necessarily reflect those of Oracle
Corporation

I believe those are the reasons why this shouldn't be used in production area but in
development stage it can be useful. If developing is well organized and you can keep
track whose is doing what then this change is possible and sometimes useful. It happens
that in development stage some columns are thought useful and added into tables but later
(before production) the architechture is changed and these new columns become useless
(and other kind of columns could be needed). But I wouldn't recommend this to anyone else
since it isn't Oracle's way and we are using their product so there I totally agree with you
Thomas. Just wanted a pro's opinion so thanks for your answer.

Rauno Received on Thu Aug 12 1999 - 01:55:19 CDT