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

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

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/bc08ee902925/
Changeset:   bc08ee902925
Branch:      master
User:        zzzeek
Date:        2014-05-29 02:01:21
Summary:     - Fixed a few edge cases which arise in the so-called "row switch"
scenario, where an INSERT/DELETE can be turned into an UPDATE.
In this situation, a many-to-one relationship set to None, or
in some cases a scalar attribute set to None, may not be detected
as a net change in value, and therefore the UPDATE would not reset
what was on the previous row.   This is due to some as-yet
unresovled side effects of the way attribute history works in terms
of implicitly assuming None isn't really a "change" for a previously
un-set attribute.  See also :ticket:`3061`. fixes #3060

Affected #:  7 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/10d4629583db/
Changeset:   10d4629583db
Branch:      rel_1_0
User:        zzzeek
Date:        2014-05-29 02:01:40
Summary:     Merge branch 'master' into rel_1_0

Affected #:  7 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/16b7f1816d54/
Changeset:   16b7f1816d54
Branch:      rel_0_9
User:        zzzeek
Date:        2014-05-29 02:01:49
Summary:     - Fixed a few edge cases which arise in the so-called "row switch"
scenario, where an INSERT/DELETE can be turned into an UPDATE.
In this situation, a many-to-one relationship set to None, or
in some cases a scalar attribute set to None, may not be detected
as a net change in value, and therefore the UPDATE would not reset
what was on the previous row.   This is due to some as-yet
unresovled side effects of the way attribute history works in terms
of implicitly assuming None isn't really a "change" for a previously
un-set attribute.  See also :ticket:`3061`. fixes #3060

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