diff options
| author | Mike Bayer <mike_mp@zzzcomputing.com> | 2017-01-13 12:43:24 -0500 |
|---|---|---|
| committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2017-01-13 14:33:42 -0500 |
| commit | afd78a37dafe8e84e23bccfb570bd758797e2142 (patch) | |
| tree | 3f194e4c19b7b0c81f7f62a67fdb1a7ca763b013 /lib/sqlalchemy/sql/schema.py | |
| parent | 0460bc79d9986132646049d8167bd5dbe3388a65 (diff) | |
| download | sqlalchemy-afd78a37dafe8e84e23bccfb570bd758797e2142.tar.gz | |
Use full column->type processing for ON CONFLICT SET clause
Fixed bug in new "ON CONFLICT DO UPDATE" feature where the "set"
values for the UPDATE clause would not be subject to type-level
processing, as normally takes effect to handle both user-defined
type level conversions as well as dialect-required conversions, such
as those required for JSON datatypes. Additionally, clarified that
the keys in the set_ dictionary should match the "key" of the column,
if distinct from the column name. A warning is emitted
for remaining column names that don't match column keys; for
compatibility reasons, these are emitted as they were previously.
Fixes: #3888
Change-Id: I67a04c67aa5f65e6d29f27bf3ef2f8257088d073
Diffstat (limited to 'lib/sqlalchemy/sql/schema.py')
0 files changed, 0 insertions, 0 deletions
