Re: Why does Postgres allow duplicate (FK) constraints - Mailing list pgsql-general

From Thomas Kellerer
Subject Re: Why does Postgres allow duplicate (FK) constraints
Date
Msg-id kish2h$nnh$1@ger.gmane.org
Whole thread Raw
In response to Re: Why does Postgres allow duplicate (FK) constraints  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Why does Postgres allow duplicate (FK) constraints
Re: Why does Postgres allow duplicate (FK) constraints
List pgsql-general
Tom Lane, 26.03.2013 17:03:
>> While I agree that this SQL should not have been written like this
>> in the first place, I wonder why Postgres doesn't actively prevent
>> this (like e.g. Oracle).
>
> If Oracle does that, they're violating the SQL standard --- there is
> nothing in the standard that supports rejecting an ALTER TABLE ADD
> CONSTRAINT on the grounds that it's redundant.  The spec only says
> you can't give two constraints the same name.

Is there anything in the standard that actively requires that you can create two "identical" constraints?

Because technically it simply doesn't make sense, does it?

Regards
Thomas

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why does Postgres allow duplicate (FK) constraints
Next
From: Tom Lane
Date:
Subject: Re: Why does Postgres allow duplicate (FK) constraints