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

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

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/164f2ad2f433/
Changeset:   164f2ad2f433
Branch:      rel_1_0
User:        zzzeek
Date:        2015-05-21 17:43:37+00:00
Summary:     flake8 some tests

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/321f39e3987d/
Changeset:   321f39e3987d
Branch:      rel_0_9
User:        zzzeek
Date:        2015-05-21 17:49:11+00:00
Summary:     flake8 some tests

(cherry picked from commit 164f2ad2f433b3d297df709d617a1fc421495921)

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/525cc6fe0247/
Changeset:   525cc6fe0247
Branch:      master
User:        zzzeek
Date:        2015-05-21 18:21:01+00:00
Summary:     - Fixed regression in the :mod:`sqlalchemy.ext.mutable` extension
as a result of the bugfix for :ticket:`3167`,
where attribute and validation events are no longer
called within the flush process.  The mutable
extension was relying upon this behavior in the case where a column
level Python-side default were responsible for generating the new value
on INSERT or UPDATE, or when a value were fetched from the RETURNING
clause for "eager defaults" mode.  The new value would not be subject
to any event when populated and the mutable extension could not
establish proper coercion or history listening.  A new event
:meth:`.InstanceEvents.refresh_flush` is added which the mutable
extension now makes use of for this use case.
fixes #3427
- Added new event :meth:`.InstanceEvents.refresh_flush`, invoked
when an INSERT or UPDATE level default value fetched via RETURNING
or Python-side default is invoked within the flush process.  This
is to provide a hook that is no longer present as a result of
:ticket:`3167`, where attribute and validation events are no longer
called within the flush process.
- Added a new semi-public method to :class:`.MutableBase`
:meth:`.MutableBase._get_listen_keys`.  Overriding this method
is needed in the case where a :class:`.MutableBase` subclass needs
events to propagate for attribute keys other than the key to which
the mutable type is associated with, when intercepting the
:meth:`.InstanceEvents.refresh` or
:meth:`.InstanceEvents.refresh_flush` events.  The current example of
this is composites using :class:`.MutableComposite`.

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.