Ensure all implicit constraints are named - Mailing list pgsql-patches

From Rod Taylor
Subject Ensure all implicit constraints are named
Date
Msg-id 1054774083.26169.6.camel@jester
Whole thread Raw
Responses Re: Ensure all implicit constraints are named
Re: Ensure all implicit constraints are named
Re: Ensure all implicit constraints are named
List pgsql-patches
If they're not, the below causes problems, as the foreign key is added
after the CHECK.  Cluster depends on the index name, so I thought it
wise to ensure all names are available, rather than leaving off the
CONSTRAINT "$n" portion for internally named constraints.

CREATE TABLE jkey (col integer primary key);
CREATE TABLE j (col integer REFERENCES jkey);
ALTER TABLE j ADD CHECK(col > 5);


This is a problem in 7.3 series as well as -Tip.

--
Rod Taylor <rbt@rbt.ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

Attachment

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pgstattuple for schemas
Next
From: Rod Taylor
Date:
Subject: Re: pgstattuple for schemas