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

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

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/8c8b22e4742d/
Changeset:   8c8b22e4742d
Branch:      rel_0_9
User:        zzzeek
Date:        2014-08-29 20:23:36
Summary:     - add a test to events within load to verify something we want
to ensure stays the same on 1.0

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/b9046a163bd9/
Changeset:   b9046a163bd9
Branch:      None
User:        zzzeek
Date:        2014-08-29 20:25:09
Summary:     - re-establish and test some behavior from previous versions, that
if a load() or refresh() event changes history (which...why...but anyway)
the state of the object is the same; currently it seems that history
gets reset but on a refresh, the object still goes into session.dirty
- simplify what we store in partials

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/9449c102768e/
Changeset:   9449c102768e
Branch:      None
User:        zzzeek
Date:        2014-08-29 21:07:11
Summary:     - reorganize how create_row_processor() communicates up to
instances(), using a named tuple it can assign to directly.  this way
we never have to worry about that structure changing anymore, though
we are still having it append (key, fn) which is kind of awkward.
- inline _populators() into instance(), it's a little verbose but
saves an fn call

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