| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Jan Wieck <wieck(at)debis(dot)com> |
| Cc: | Vassiliadis Spyros <aceteam(at)it(dot)teithe(dot)gr>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: referencial integrity constraint bug in version 7.0 beta 5 |
| Date: | 2000-05-01 19:50:57 |
| Message-ID: | Pine.LNX.4.21.0005012133430.389-100000@localhost.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Heflin | 2000-05-01 20:11:45 | multiple queries using PHP |
| Previous Message | Peter Eisentraut | 2000-05-01 19:50:47 | Re: Performance/Reliability statistics? |