Mar 2019

1 commit
Fix optimization of foreign-key on update actions
18 Mar 2019Peter Eisentrautmaster12beta1REL_19_STABLE12beta1REL_18_STABLE12beta1REL_17_STABLE12beta1REL_16_STABLE12beta1REL_15_STABLE12beta1REL_14_STABLE12beta1REL_13_STABLE12beta1+1 more
LLM analysis, 100% suremodified before commitlight changesfrom patchset #80 of 1 reviewer saw the final version

The commit combines both patches from #8, preserving the datum_image_eq() extraction and revised ri_KeysEqual() logic. Beyond rebasing, the regression-test comment in foreign_key.sql and foreign_key.out changes from "should update" to "should have updated".

  • Tom Lanesaw an earlier versionLLM analysis, 99% sureIn #3, he criticized the CASCADE-only comparison rule in #1, prompting the broader primary-key comparison logic adopted in #8.

Credits across 1 commit

Author
Peter EisentrautLLM1
Committer
Peter Eisentraut1

N LLM means N of the credits come from LLM analysis, not from commit trailers.