Re: Drop constraints CASCADE not working on 10g Express

From: QDL <qdl_at_qdl.qdl>
Date: Fri, 24 Nov 2006 17:01:15 +0100
Message-ID: <456717d8$0$13751$4fafbaef@reader3.news.tin.it>

> Paolo, CASCADE keyword is/was not related to the index retaining/dropping
> of primary key. To drop/retain index you have to specify DROP INDEX or
> KEEP INDEX, you can look it up
> http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_3001.htm#i2103845
> I believe, it was discussed here some time ago about changed behaviour
> from 9i to 10g (in 9i default was DROP INDEX, in 10g - the opposite iirc).

Thanx for answering, I guess I will have to change my DBUpgrade program... To make it work i will have to remove CASCADE and issue an explicit DROP INDEX after removing the constraint...

This will make it work on both 9i and 10g, correct?

> Best regards
> Maxim

Thanx a lot
Paolo Received on Fri Nov 24 2006 - 10:01:15 CST