Consider CREATE TABLE foo (f1 int primary key);
CREATE TABLE bar (f1 int references foo); DROP TABLE foo RESTRICT; Should this succeed? Or should it be necessary to say DROP CASCADE to get rid of the foreign-key reference to foo? Our historical behavior is to allow the drop, while issuing a notice about implicit deletion of triggers. But I think SQL92 intends that CASCADE should be required. (If you deduce from this question that a lot of Rod Taylor's pg_depend patch is working here, you are right...) regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]