| From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
|---|---|
| To: | Joel Jacobson <joel(at)compiler(dot)org> |
| Cc: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Foreign key joins revisited |
| Date: | 2021-12-27 16:03:43 |
| Message-ID: | CAMsGm5eQBAsHERR7fKgYrTDa=9SMmcDmMZ=0U+G8AZ_SAQHvMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 27 Dec 2021 at 10:20, Joel Jacobson <joel(at)compiler(dot)org> wrote:
> Foreign key constraint names have been given the same names as the
> referenced tables.
>
While I agree this could be a simple approach in many real cases for having
easy to understand FK constraint names, I wonder if for illustration and
explaining the feature if it might work better to use names that are
completely unique so that it's crystal clear that the names are constraint
names, not table names.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-12-27 16:10:21 | default to to ON_ERROR_STOP=on (Re: psql: exit status with multiple -c and -f) |
| Previous Message | Tom Lane | 2021-12-27 15:54:25 | Re: why does reindex invalidate relcache without modifying system tables |