delta/python-packages/sqlalchemy.git/lib/sqlalchemy/orm/mapper.py, branch pr/318

Ensure mapper.polymorphic_on is polymorphic_prop.columns[0]

2016-09-21T21:57:38+00:00

Fixed bug where joined eager loading would fail for a polymorphically-
loaded mapper, where the polymorphic_on was set to an un-mapped
expression such as a CASE expression.

Change-Id: Iffe68196aaac592165c89684f09f4c06cd78ce54
Fixes: #3800

Add the "triggering mapper" to the configure_mappers error message.

2016-09-20T16:11:11+00:00

There are cases where the originating mapper name is not
present in the exception message, such as relationship initialization
against an unmapped class.   Ensure the originating mapper is named
in the string output.

Pull-request: https://github.com/zzzeek/sqlalchemy/pull/298
Change-Id: I9f23bfa90b26dde9229ab7ec812eec9ceae48153

Raise when two validators conflict

2016-08-26T16:56:01+00:00

Two @validates decorators that make use of the same name
is not supported.  Raise an exception.

Change-Id: Ia3e89ffdc9ef345a0de258e2ac0ac5e0bd421c61
Fixes: #3776

Allow Table._reset_exported to silently pass

2016-07-25T03:17:11+00:00

Fixed bug in :class:`.Table` where the internal method
``_reset_exported()`` would corrupt the state of the object.  This
method is intended for selectable objects and is called by the ORM
in some cases; an erroneous mapper configuration would could lead the
ORM to call this on on a :class:`.Table` object.

Change-Id: I63fa34ee0cdf16358bb125c556390df79758bcbc
Fixes: #3755

Corrects some references in ORM documentation.

2016-05-04T00:46:20+00:00

Deprecate Mapper.order_by

2016-04-19T22:17:45+00:00

This is an old parameter no longer relevant to how SQLAlchemy
works, once the Query object was introduced.  By deprecating it
we establish that we aren't supporting non-working use cases
and that we encourage applications to move off of the use of this
parameter.

Fixes: #3394
Change-Id: I25b9a38142a1537bbcb27d3e8b66a8b265140072

- happy new year

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

- Added new parameter :paramref:`.orm.mapper.passive_deletes` to

2016-01-20T22:59:56+00:00

available mapper options.   This allows a DELETE to proceed
for a joined-table inheritance mapping against the base table only,
while allowing for ON DELETE CASCADE to handle deleting the row
from the subclass tables.
fixes #2349

- Fixed issue where two same-named relationships that refer to

2016-01-19T18:34:42+00:00

a base class and a concrete-inherited subclass would raise an error
if those relationships were set up using "backref", while setting up the
identical configuration using relationship() instead with the conflicting
names would succeed, as is allowed in the case of a concrete mapping.
fixes #3630

- Fixed bug in :meth:`.Update.return_defaults` which would cause all

2015-12-14T22:30:21+00:00

insert-default holding columns not otherwise included in the SET
clause (such as primary key cols) to get rendered into the RETURNING
even though this is an UPDATE.

- Major fixes to the :paramref:`.Mapper.eager_defaults` flag, this
flag would not be honored correctly in the case that multiple
UPDATE statements were to be emitted, either as part of a flush
or a bulk update operation.  Additionally, RETURNING
would be emitted unnecessarily within update statements.

fixes #3609