Re: Problem with non-unique constraint names

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Ken Winter <ken(at)sunward(dot)org>
Cc: PostgreSQL pg-general List <pgsql-general(at)postgresql(dot)org>, kwinter(at)dhat(dot)org
Subject: Re: Problem with non-unique constraint names
Date: 2009-02-14 22:00:16
Message-ID: dcc563d10902141400l2541810eo120908396e3530dc@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bob Pawley 2009-02-14 22:10:42 pg_hba reload
Previous Message Ken Winter 2009-02-14 21:16:54 Problem with non-unique constraint names