| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgreSQL(dot)org>, <pgsql-sql(at)postgreSQL(dot)org> |
| Subject: | Re: Uniqueness of rule, constraint, and trigger names |
| Date: | 2002-03-04 22:13:18 |
| Message-ID: | 20020304140956.F80841-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
On Mon, 4 Mar 2002, Tom Lane wrote:
> For constraints, we'd need to change the code to be more careful to
> generate unique names for unnamed constraints. That doesn't seem
Another question would be what to do with inherited constraints that
conflict in multiple inheritance cases. It'd probably be safe to rename
those on the child table to be unique, but then drop constraint may
become more involved (and the error messages no longer use the name
given by the user for either constraint).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-03-04 22:18:32 | Re: Uniqueness of rule, constraint, and trigger names |
| Previous Message | Tom Lane | 2002-03-04 22:05:23 | Re: Database Caching |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-03-04 22:18:32 | Re: Uniqueness of rule, constraint, and trigger names |
| Previous Message | Rod Taylor | 2002-03-04 21:40:16 | Re: [HACKERS] Uniqueness of rule, constraint, and trigger names |