Re: Information Schema and constraint names not unique - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Information Schema and constraint names not unique
Date
Msg-id 29215.1068220741@sss.pgh.pa.us
Whole thread Raw
In response to Re: Information Schema and constraint names not unique  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Information Schema and constraint names not unique
Re: Information Schema and constraint names not unique
Re: Information Schema and constraint names not
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.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


pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: Performance features the 4th
Next
From: Bruce Momjian
Date:
Subject: Re: Experimental ARC implementation