I'm just wondering if the best way to handle a rollback of added columns is
to alter the table to mark the column as unused and then drop the unused
columns via ALTER TABLE t1 DROP UNUSED COLUMNS; or would the ideal thing be
to export the table(s) before adding the columns and then reimport, although
that could get very sticky since I'd be dealing with the whole table and
associated constraints instead of just the columns I'm trying to remove. I
basically want to have both a rollout and a rollback script for an upcoming
rather large move to production. Your input would be greatly appreciated.
TIA,
Richard Huntley
E-mail: [EMAIL PROTECTED]
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Richard Huntley
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
