Re: referencial integrity constraint bug in version 7.0 beta 5
От | Peter Eisentraut |
---|---|
Тема | Re: referencial integrity constraint bug in version 7.0 beta 5 |
Дата | |
Msg-id | Pine.LNX.4.21.0005012133430.389-100000@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: referencial integrity constraint bug in version 7.0 beta 5 (wieck@debis.com (Jan Wieck)) |
Ответы |
Re: referencial integrity constraint bug in version 7.0 beta
55
|
Список | pgsql-general |
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
В списке pgsql-general по дате отправления: