Re: Problem with non-unique constraint names - Mailing list pgsql-general

From Scott Marlowe
Subject Re: Problem with non-unique constraint names
Date
Msg-id dcc563d10902141400l2541810eo120908396e3530dc@mail.gmail.com
Whole thread Raw
In response to Problem with non-unique constraint names  ("Ken Winter" <ken@sunward.org>)
List pgsql-general
I think your two alternatives are to either make sure no constraint
names are duplicated, or add a unique key for conname to
pg_constraint.  I didn;t know constraint name was a SQL requirement.
I can see how the information_schema would be designed to assume they
were unique if it was.

pgsql-general by date:

Previous
From: "Ken Winter"
Date:
Subject: Problem with non-unique constraint names
Next
From: "Bob Pawley"
Date:
Subject: pg_hba reload