Thread
Commits
-
Fix FK comment think-o
- 6bcd1d9f30c0 15.2 landed
- 5e9b12205999 16.0 landed
-
Think-o in foreign key comments
Paul A Jungwirth <pj@illuminatedcomputing.com> — 2022-12-02T22:18:51Z
Hello, I noticed a few places in the new foreign key code where a comment says "the ON DELETE SET NULL/DELETE clause". I believe it should say "ON DELETE SET NULL/DEFAULT". These comments were added in d6f96ed94e7, "Allow specifying column list for foreign key ON DELETE SET actions." Here is a patch to correct them. I don't think you usually create a commitfest entry for tiny fixes like this, right? But if you'd like one please let me know and I'll add it. Yours, -- Paul ~{:-) pj@illuminatedcomputing.com -
Re: Think-o in foreign key comments
Ian Lawrence Barwick <barwick@gmail.com> — 2022-12-03T04:59:30Z
2022年12月3日(土) 7:19 Paul Jungwirth <pj@illuminatedcomputing.com>: > > Hello, > > I noticed a few places in the new foreign key code where a comment says > "the ON DELETE SET NULL/DELETE clause". I believe it should say "ON > DELETE SET NULL/DEFAULT". > > These comments were added in d6f96ed94e7, "Allow specifying column list > for foreign key ON DELETE SET actions." Here is a patch to correct them. LGTM. I do notice the same patch adds the function "validateFkOnDeleteSetColumns" but the name in the comment preceding it is "validateFkActionSetColumns", might as well fix that the same time. > I don't think you usually create a commitfest entry for tiny fixes like > this, right? But if you'd like one please let me know and I'll add it. From experience usually a committer will pick up trivial fixes like this within a few days, but if it escapes notice for more than a couple of weeks a reminder and/or CF entry might be useful to make sure it doesn't get forgotten. Regards Ian Barwick
-
Re: Think-o in foreign key comments
Peter Eisentraut <peter.eisentraut@enterprisedb.com> — 2022-12-07T16:11:52Z
On 03.12.22 05:59, Ian Lawrence Barwick wrote: > 2022年12月3日(土) 7:19 Paul Jungwirth <pj@illuminatedcomputing.com>: >> I noticed a few places in the new foreign key code where a comment says >> "the ON DELETE SET NULL/DELETE clause". I believe it should say "ON >> DELETE SET NULL/DEFAULT". >> >> These comments were added in d6f96ed94e7, "Allow specifying column list >> for foreign key ON DELETE SET actions." Here is a patch to correct them. > > LGTM. > > I do notice the same patch adds the function "validateFkOnDeleteSetColumns" > but the name in the comment preceding it is "validateFkActionSetColumns", > might as well fix that the same time. Committed with that addition and backpatched to PG15.