Re: ENABLE NOVALIDATE behaviour bug

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Fri, 2 Jul 2004 08:49:48 +0100
Message-ID: <008301c46009$266657b0$7102a8c0@Primary>

Note in-line.

Regards

Jonathan Lewis

http://www.jlcomp.demon.co.uk

http://www.jlcomp.demon.co.uk/faq/ind_faq.html The Co-operative Oracle Users' FAQ

http://www.jlcomp.demon.co.uk/seminar.html Optimising Oracle Seminar - schedule updated May 1st

Original Message ----- From: "Jacques Kilchoer" <Jacques.Kilchoer_at_quest.com> To: <oracle-l_at_freelists.org> Sent: Wednesday, June 30, 2004 11:22 PM Subject: RE: ENABLE NOVALIDATE behaviour bug

This is probably nit-picking, but what purpose does step 2 (add constraint disable) serve?

>> Book-keeping - I didn't have anything subtle in
>> mind, and you're probably right that it's redundant

Wouldn't this be effectively the same? Or is there some subtlety that is going over my head?

    add column
    update the column where null in batches - committing     add the default
    add constraint enable novalidate
    update any columns still null
    validate the constraint
=20

Please see the official ORACLE-L FAQ: http://www.orafaq.com

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Fri Jul 02 2004 - 02:47:02 CDT