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

From Tom Lane
Subject Re: issue about information_schema REFERENTIAL_CONSTRAINTS
Date
Msg-id 29605.1284266432@sss.pgh.pa.us
Whole thread Raw
In response to Re: issue about information_schema REFERENTIAL_CONSTRAINTS  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: issue about information_schema REFERENTIAL_CONSTRAINTS  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
Robert Haas <robertmhaas@gmail.com> writes:
> 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.  This 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?

No, because those syntaxes constrain the choice to one single
constraint.  Perhaps if the SQL committee had designed 'em,
there'd be an issue; but they are Postgres-isms.

            regards, tom lane

pgsql-bugs by date:

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