delta/python-packages/sqlalchemy.git/lib/sqlalchemy/ext/declarative/base.py, branch pr_github_383

Warn when declared_attr.cascading detected on mapped class

2017-06-06T21:16:58+00:00

A warning is emitted if the :attr:`.declared_attr.cascading` modifier
is used with a declarative attribute that is itself declared on
a class that is to be mapped, as opposed to a declarative mixin
class or ``__abstract__`` class.  The :attr:`.declared_attr.cascading`
modifier currently only applies to mixin/abstract classes.

Also add a test for @declared_attr.cascading when used on an attribute
on __abstract__.

Change-Id: Ib1b9dbe373e8be1cf24eadfed224a8988b3cd95d
Fixes: #3847

Don't hard-evaluate non-ORM @declared_attr for AbstractConcreteBase

2017-05-26T17:28:15+00:00

Fixed bug where using :class:`.declared_attr` on an
:class:`.AbstractConcreteBase` where a particular return value were some
non-mapped symbol, including ``None``, would cause the attribute
to hard-evaluate just once and store the value to the object
dictionary, not allowing it to invoke for subclasses.   This behavior
is normal when :class:`.declared_attr` is on a mapped class, and
does not occur on a mixin or abstract class.  Since
:class:`.AbstractConcreteBase` is both "abstract" and actually
"mapped", a special exception case is made here so that the
"abstract" behavior takes precedence for :class:`.declared_attr`.

Change-Id: I6160ebb3a52c441d6a4b663c8c9bbac6d37fa417
Fixes: #3848

Protect against cls weakref becoming None

2017-05-08T22:36:57+00:00

Protected against testing "None" as a class in the case where
declarative classes are being garbage collected and new
automap prepare() operations are taking place concurrently, very
infrequently hitting a weakref that has not been fully acted upon
after gc.

Change-Id: I32e1dfc5ac46bac4127fe808cfd18368e2fad9dd

Union the exclude_properties of the inheriting mapper in declarative

2017-01-30T22:28:22+00:00

Fixed bug where the "automatic exclude" feature of declarative that
ensures a column local to a single table inheritance subclass does
not appear as an attribute on other derivations of the base would
not take effect for multiple levels of subclassing from the base.

Change-Id: Ibf67b631b4870dd1bd159f7d6085549d299fffe0
Fixes: #3895

update for 2017 copyright

2017-01-04T17:39:24+00:00

Change-Id: I4e8c2aa8fe817bb2af8707410fa0201f938781de

Mention the correct way of adding multiple attributes which refer to the same column

2016-04-07T10:57:14+00:00

- happy new year

2016-01-29T16:20:22+00:00

- Fixed bug in :class:`.AbstractConcreteBase` extension where

2015-07-13T19:39:04+00:00

a column setup on the ABC base which had a different attribute
name vs. column name would not be correctly mapped on the final
base class.   The failure on 0.9 would be silent whereas on
1.0 it raised an ArgumentError, so may not have been noticed
prior to 1.0.
fixes #3480

- Fixed a regression regarding the :meth:`.MapperEvents.instrument_class`

2015-04-26T22:22:41+00:00

event where its invocation was moved to be after the class manager's
instrumentation of the class, which is the opposite of what the
documentation for the event explicitly states.  The rationale for the
switch was due to Declarative taking the step of setting up
the full "instrumentation manager" for a class before it was mapped
for the purpose of the new ``@declared_attr`` features
described in :ref:`feature_3150`, but the change was also made
against the classical use of :func:`.mapper` for consistency.
However, SQLSoup relies upon the instrumentation event happening
before any instrumentation under classical mapping.
The behavior is reverted in the case of classical and declarative
mapping, the latter implemented by using a simple memoization
without using class manager.
fixes #3388

- add the "strict" version of this lookup for abstract as well,

2015-04-24T21:03:34+00:00

fixes #3383