Jan Wieck writes:
> Deny column dropping if column in question is used by an
> FK constraint.
Actually, all the DROP commands in SQL have a RESTRICT/CASCADE choice that
ought to take care of this. Unfortunately, the PostgreSQL behavior is more
like `dangle' with an occasional `restrict' but nothing really consistent.
> Propagate column or table renaming to FK constraints.
Don't you refer to them by oid?
> Emit a warning if at FK creation time no UNIQUE index
> exists over referenced PK attributes.
That should actually be an error. (SQL clause 11.8 Syntax rule 2)
--
Peter Eisentraut Sernanders väg 10:115
peter_e@gmx.net 75262 Uppsala
http://yi.org/peter-e/ Sweden
