]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
render col name in on conflict set clause, not given key
authorMike Bayer <mike_mp@zzzcomputing.com>
Fri, 13 May 2022 20:08:34 +0000 (16:08 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Sun, 15 May 2022 21:27:27 +0000 (17:27 -0400)
commit927abc3b33f10464ed04db3d7a454faeb6e729f2
treef7d6b727a3178c3c01ccc9e78b0f8c957ed1fefa
parent257de6ebe15d3076e19f05f93c5b3c7fae25a4d3
render col name in on conflict set clause, not given key

Fixed bug where the PostgreSQL :meth:`_postgresql.Insert.on_conflict`
method and the SQLite :meth:`_sqlite.Insert.on_conflict` method would both
fail to correctly accommodate a column with a separate ".key" when
specifying the column using its key name in the dictionary passed to
``set_``, as well as if the :attr:`_sqlite.Insert.excluded` or
:attr:`_postgresql.Insert.excluded` collection were used as the dictionary
directly.

Fixes: #8014
Change-Id: I67226aeedcb2c683e22405af64720cc1f990f274
doc/build/changelog/unreleased_14/8014.rst [new file with mode: 0644]
lib/sqlalchemy/dialects/postgresql/base.py
lib/sqlalchemy/dialects/sqlite/base.py
test/dialect/postgresql/test_compiler.py
test/dialect/test_sqlite.py