Droppping a Foreign Key produces inconsistent results
I notice that using ALTER TABLE to drop a foreign key constraint removes the records from INFORMATION_SCHEMA.KEY_COLUMN_USAGE.
Sometimes, the index on the referencing column(s) seems to get "left behind", in other words an entry is created in the INFORMATION_SCHEMA.STATISTICS table when the foreign key is dropped.
I would understand this behaviour if it was consistent, what puzzles me is why it only happens sometimes. Any ideas, or should I investigate further to identify a pattern?
Duncan
Subject
Views
Written By
Posted
Droppping a Foreign Key produces inconsistent results
2348
January 08, 2009 06:23AM
1574
January 08, 2009 07:57AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.