|From:||Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>|
|To:||Paul Martinez <hellopfm(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: PATCH: Include all columns in default names for foreign key constraints.|
|Views:||Raw Message | Whole Thread | Download mbox|
On 13/01/2019 01:55, Paul Martinez wrote:
> The two constraints have nearly identical names. With my patch the default names
> will include both column names, so we have we will instead have this output:
> Foreign-key constraints:
> "comments_tenant_id_commenter_id_fkey" FOREIGN KEY (tenant_id,
> commenter_id) REFERENCES users(tenant_id, id)
> "comments_tenant_id_post_id_fkey" FOREIGN KEY (tenant_id, post_id)
> REFERENCES posts(tenant_id, id)
> This makes the default names for foreign keys in line with the default names
> for indexes. Hopefully an uncontroversial change!
I think this is a good change.
> I pretty much just copied and pasted the implementation from
> ChooseIndexNameAddition and placed it in src/backend/commands/tablecmds.c.
The use of "name2" in the comment doesn't make sense outside the context
of indexcmds.c. Maybe rewrite that a bit.
> Regression tests are in src/test/regress/sql/foreign_key.sql. I create two
> composite foreign keys on table, one via the CREATE TABLE statement, and the
> other in a ALTER TABLE statement. The generated names of the constraints are
> then queried from the pg_constraint table.
Existing regression tests already exercise this, and they are failing
all over the place because of the changes of the generated names. That
is to be expected. You should investigate those failures and adjust the
"expected" files. Then you probably don't need your additional tests.
It might be worth having a test that runs into the 63-character length
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
|Next Message||Amit Khandekar||2019-02-08 10:17:33||Re: Pluggable Storage - Andres's take|
|Previous Message||Ashutosh Sharma||2019-02-08 10:07:00||Re: ON SELECT rule on a table without columns|