> CREATE SEQUENCE conn_id_seq;
> CREATE TABLE conn (
> id INTEGER NOT NULL DEFAULT nextval('conn_id_seq'),
> name VARCHAR(40),
> CONSTRAINT conn_friend_fkey FOREIGN KEY(name)
> REFERENCES friend(name)
> ON UPDATE CASCADE
> ON DELETE RESTRICT
I believe we interpreted restrict as being such that you
can't defer it. No action specification for delete
probably would do what you wanted. (We may also be wrong
about restrict, but the above would be a workaround in any case)
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
