[Sqlalchemy-commits] commit/sqlalchemy: 2 new changesets

[Bitbucket <com...@bi...>]

2 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/afd78a37dafe/
Changeset:   afd78a37dafe
Branch:      None
User:        zzzeek
Date:        2017-01-13 19:33:42+00:00
Summary:     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

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/9ef1913ed647/
Changeset:   9ef1913ed647
Branch:      master
User:        zzzeek
Date:        2017-01-13 20:47:00+00:00
Summary:     Merge "Use full column->type processing for ON CONFLICT SET clause"
Affected #:  5 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.