> All these cases can be addressed by the simple expedient of declaring a
> foreign key inactive.

If application developer has names of all foreign keys, it no longer matters
what to execute:

ALTER TABLE <table name> ALTER CONSTRAINT <foreign key name> INAVTIVE;

or

ALTER TABLE <table name> DROP CONSTRAINT <foreign key name>

The talk is about a global switch that triggers all constrains inactive
without a need to walk through all system tables and deactivating each
constraint separately.

Roman