Mike Bayer afd78a37da 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

2017-01-13 14:33:42 -05:00

..

__init__.py

…

test_compiler.py

Use full column->type processing for ON CONFLICT SET clause

2017-01-13 14:33:42 -05:00

test_dialect.py

Repair PG BIGSERIAL w/ TypeDecorator, Variant

2016-07-04 16:54:01 -04:00

test_on_conflict.py

Use full column->type processing for ON CONFLICT SET clause

2017-01-13 14:33:42 -05:00

test_query.py

Add support for server side cursors to mysqldb and pymysql

2016-11-10 12:09:27 -05:00

test_reflection.py

Don't set pg autoincrement if type affinity is not Integer

2016-10-20 17:38:22 -04:00

test_types.py

Allow the value 0 for Postgresql TIME/TIMESTAMP precision

2016-11-23 09:48:34 -05:00