Re: Deferred constraint question

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Sat, 26 Jun 1999 00:39:48 +0100
Message-ID: <930354380.12945.0.nnrp-08.9e984b29@news.demon.co.uk>

I had jumped to the conclusion that

set constraint XX immediate

would always work, even if previously
entered data was in breach of the constraint.

(cp. ENABLE CONSTRAINT NOVALIDATE)

The concepts manual points out '

'' If any constraint fails the check, and error is signalled; at that point a COMMIT would cause the whole transaction to roll back''.

Because it did NOT say that the constraint's status would not change, I assumed incorrectly that it would.

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

Thomas Kyte wrote in message <3778d653.89524579_at_newshost.us.oracle.com>...
>>***ORA-02290: check constraint (DEMO.JPL_CK_N1) violated
>>*** Change it back to immediate, and Oracle finds the bad row
>>*** Note: it is not supposed to do anything but report it just yet.

>
>why do you say that? Its reporting an error saying "i cannot set the
constraint
>to immediate because there is data in there that doesn't work with
immediate".
>
Received on Fri Jun 25 1999 - 18:39:48 CDT