On Mon, 6 Oct 2003, Ara Anjargolian wrote:
> Also notice that the foreign key constraint is not declared until after
> the table definition. This error does not show up if the foreign key is
> added when the content table is defined.
It works the same for me as a table constraint or as an alter as long as
on update cascade is given in both cases. It'd be nice to fail at
constraint creation time if on update cascade is given and the type on the
primary key table wasn't assignment convertable to the type on the foreign
key table.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
