| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Information Schema and constraint names not unique |
| Date: | 2003-11-07 15:59:01 |
| Message-ID: | 29215.1068220741@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I think there are several of them from this thread:
> . make autogenerated column constraint names unique per table (by adding
> "_$n" ?)
Check.
> . add tableoid or tablename to information_schema.{check_constraints,
> referential_constraints} (I think those are the only places where it
> would be needed, from my quick skimming).
> . add tableoid or tablename to autogenerated table constraint names
These are mutually exclusive --- I see no reason to do both.
> Using tableoid instead of tablename avoids renaming problems, but makes
> the names horribly opaque IMNSHO.
Agreed. I think using the OIDs would be a horrible choice.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-11-07 15:59:26 | Re: Experimental ARC implementation |
| Previous Message | Jan Wieck | 2003-11-07 15:56:02 | Re: Performance features the 4th |