[Sqlalchemy-commits] commit/sqlalchemy: zzzeek: Rewrite migration notes for [ticket:3514]

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

1 new commit in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/76ec285ba452/
Changeset:   76ec285ba452
Branch:      None
User:        zzzeek
Date:        2016-10-19 17:09:16+00:00
Summary:     Rewrite migration notes for [ticket:3514]

The change to "evaluates none" datatypes in the ORM was
not fully described in the migration notes, missing the
key behavioral change that a column which is missing a default
entirely will not receive a value for a missing JSON column now.
The issue here touched upon a revisit of the assumptions
in [ticket:3514], but overall the old behavior "worked" mostly
because the ORM wants to explicitly render NULL into an INSERT
for column values that are missing, which itself is a legacy
behavior which should be considered for possible removal in
a future major release.  Given that "missing ORM value + no
column default set up == dont put it in the INSERT" would be
the most intuitive behavior, the move in [ticket:3514] represents
a step in this direction.

Change-Id: I454d5bb0773bd73d9864925dcc47f1f0810e33ba
Fixes: #3830

Affected #:  4 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.