delta/python-packages/sqlalchemy.git/test/ext/test_mutable.py, branch rel_1_1

Add tests for ARRAY propagate events re. MutableList

2017-12-04T22:42:04+00:00

Issue #4141 appears in version 1.2, however we are adding the
MutableList test for it to 1.1 as well.  The metadata test
does not apply as in 1.1 ARRAY is not a SchemaEventTarget.

Change-Id: If8c57615860883837f6cf72661e46180a77778c1
(cherry picked from commit 14bb6eae364f41b6acbce782ebf5f984b9364af9)

Ensure we check that SQL expression has an .info attribute

2017-04-04T13:07:14+00:00

Fixed regression released in 1.1.8 due to :ticket:`3950` where the
deeper search for information about column types in the case of a
"schema type" or a :class:`.TypeDecorator` would produce an attribute
error if the mapping also contained a :obj:`.column_property`.

Change-Id: I38254834d3d79c9b339289a8163eb4789ec4c931
Fixes: #3956
(cherry picked from commit d13734add349ec6763cce8b194806c5afe988000)

Track SchemaEventTarget types in as_mutable()

2017-03-30T21:52:56+00:00

Fixed bug in :mod:`sqlalchemy.ext.mutable` where the
:meth:`.Mutable.as_mutable` method would not track a type that had
been copied using :meth:`.TypeEngine.copy`.  This became more of
a regression in 1.1 compared to 1.0 because the :class:`.TypeDecorator`
class is now a subclass of :class:`.SchemaEventTarget`, which among
other things indicates to the parent :class:`.Column` that the type
should be copied when the :class:`.Column` is.  These copies are
common when using declarative with mixins or abstract classes.

Change-Id: Ib04df862c58263185dbae686c548fea3e12c46f1
Fixes: #3950
(cherry picked from commit 07b63894cb8ff9529b406f196b5d7cb9af209e9e)

Make all tests to be PEP8 compliant

2017-02-07T16:21:56+00:00

tested using pycodestyle version 2.2.0

Fixes: #3885
Change-Id: I5df43adc3aefe318f9eeab72a078247a548ec566
Pull-request: https://github.com/zzzeek/sqlalchemy/pull/343

Add `sqlalchemy.ext.mutable.MutableSet`

2016-02-13T12:28:50+00:00

from https://bitbucket.org/zzzeek/sqlalchemy/issues/3297

Add `sqlalchemy.ext.mutable.MutableList`

2016-02-13T12:28:46+00:00

- Further fixes to :ticket:`3605`, pop method on :class:`.MutableDict`,

2015-12-17T16:24:35+00:00

where the "default" argument was not included.
fixes #3605

- Added support for the ``dict.pop()`` and ``dict.popitem()`` methods

2015-12-11T16:21:46+00:00

to the :class:`.mutable.MutableDict` class.
fixes #3605

- Fixed regression in the :mod:`sqlalchemy.ext.mutable` extension

2015-05-21T18:21:01+00:00

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`.

flake8 some tests

2015-05-21T17:43:37+00:00