From: Mike Bayer Date: Mon, 11 Oct 2021 16:34:02 +0000 (-0400) Subject: Add missing changelog file for #7153 X-Git-Tag: rel_1_4_26~25 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=c94a4b2cea888903fdc9595917b10c4fa8b36afc;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git Add missing changelog file for #7153 Fixes: #7153 Change-Id: I613d3179781344923add904cbdca87aff89eee83 --- diff --git a/doc/build/changelog/unreleased_14/7153.rst b/doc/build/changelog/unreleased_14/7153.rst new file mode 100644 index 0000000000..762fb638dc --- /dev/null +++ b/doc/build/changelog/unreleased_14/7153.rst @@ -0,0 +1,25 @@ +.. change:: + :tags: bug, sql + :tickets: 7153 + + Adjusted the "column disambiguation" logic that's new in 1.4, where the + same expression repeated gets an "extra anonymous" label, so that the logic + more aggressively deduplicates those labels when the repeated element + is the same Python expression object each time, as occurs in cases like + when using "singleton" values like :func:`_sql.null`. This is based on + the observation that at least some databases (e.g. MySQL, but not SQLite) + will raise an error if the same label is repeated inside of a subquery. + +.. change:: + :tags: bug, orm + :tickets: 7154 + + Related to :ticket:`7153`, fixed an issue where result column lookups would + fail for "adapted" SELECT statements that selected for "constant" value + expressions most typically the NULL expression, as would occur in such + places as joined eager loading in conjunction with limit/offset. This was + overall a regression due to issue :ticket:`6259` which removed all + "adaption" for constants like NULL, "true", and "false" when rewriting + expressions in a SQL statement, but this broke the case where the same + adaption logic were used to resolve the constant to a labeled expression + for the purposes of result set targeting.