Re: issue about information_schema REFERENTIAL_CONSTRAINTS - Mailing list pgsql-bugs

From Robert Haas
Subject Re: issue about information_schema REFERENTIAL_CONSTRAINTS
Date
Msg-id AANLkTin1vvc2Yfs3mBnmL_yCq3KRuMbo4zzGihsNcuQZ@mail.gmail.com
Whole thread Raw
In response to Re: issue about information_schema REFERENTIAL_CONSTRAINTS  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: issue about information_schema REFERENTIAL_CONSTRAINTS
List pgsql-bugs
On Tue, Aug 31, 2010 at 10:46 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> We are not going to try to enforce uniqueness. =A0This has been debated
> before, and most people like the current behavior just fine, or at least
> better than the alternatives.

Really?  I thought the issue was that no one had figured out how to do
it, or that no one had written the patch, not that anyone thought the
current behavior was particularly desirable.  What happens if you say
ALTER TABLE .. DROP CONSTRAINT or COMMENT ON CONSTRAINT?  You just
pick one at random?  That's really what most people want?

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

pgsql-bugs by date:

Previous
From: Josh Berkus
Date:
Subject: 9.0 Bug: cannot build against python3.1, with two versions of python in the environment
Next
From: Tom Lane
Date:
Subject: Re: issue about information_schema REFERENTIAL_CONSTRAINTS