delta/python-packages/sqlalchemy.git/test/orm/test_unitofwork.py, branch pr/263

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

- The system by which a :class:`.Column` considers itself to be an

2015-10-07T14:02:45+00:00

"auto increment" column has been changed, such that autoincrement
is no longer implicitly enabled for a :class:`.Table` that has a
composite primary key.  In order to accommodate being able to enable
autoincrement for a composite PK member column while at the same time
maintaining SQLAlchemy's long standing behavior of enabling
implicit autoincrement for a single integer primary key, a third
state has been added to the :paramref:`.Column.autoincrement` parameter
``"auto"``, which is now the default. fixes #3216
- The MySQL dialect no longer generates an extra "KEY" directive when
generating CREATE TABLE DDL for a table using InnoDB with a
composite primary key with AUTO_INCREMENT on a column that isn't the
first column;  to overcome InnoDB's limitation here, the PRIMARY KEY
constraint is now generated with the AUTO_INCREMENT column placed
first in the list of columns.

- Fixed regression within the flush process when an attribute were

2015-04-29T18:00:16+00:00

set to a SQL expression for an UPDATE, and the SQL expression when
compared to the previous value of the attribute would produce a SQL
comparison other than ``==`` or ``!=``, the exception "Boolean value
of this clause is not defined" would raise.   The fix ensures that
the unit of work will not interpret the SQL expression in this way.
fixes #3402

Small improvement on FlushError can't update error message

2014-11-06T20:14:17+00:00

Output in the error message the table name and the column name.

Small improvement on FlushError can't delete error message

2014-11-05T12:23:03+00:00

Output in the error message the table name and the column name.

- UPDATE statements can now be batched within an ORM flush

2014-08-15T00:47:49+00:00

into more performant executemany() call, similarly to how INSERT
statements can be batched; this will be invoked within flush
to the degree that subsequent UPDATE statements for the
same mapping and table involve the identical columns within the
VALUES clause, as well as that no VALUES-level SQL expressions
are embedded.
- some other inlinings within persistence.py

- use a variant with expected collation here for mysql

2014-07-25T16:02:05+00:00

- Additional checks have been added for the case where an inheriting

2014-06-20T22:47:28+00:00

mapper is implicitly combining one of its column-based attributes
with that of the parent, where those columns normally don't necessarily
share the same value.  This is an extension of an existing check that
was added via :ticket:`1892`; however this new check emits only a
warning, instead of an exception, to allow for applications that may
be relying upon the existing behavior.
fixes #3042

Fix many typos throughout the codebase

2014-04-26T20:13:13+00:00

Found using: https://github.com/intgr/topy

- Added new parameter :paramref:`.mapper.confirm_deleted_rows`. Defaults

2014-03-28T22:00:35+00:00

to True, indicates that a series of DELETE statements should confirm
that the cursor rowcount matches the number of primary keys that should
have matched;  this behavior had been taken off in most cases
(except when version_id is used) to support the unusual edge case of
self-referential ON DELETE CASCADE; to accomodate this, the message
is now just a warning, not an exception, and the flag can be used
to indicate a mapping that expects self-refererntial cascaded
deletes of this nature.  See also :ticket:`2403` for background on the
original change. re: #2403 fix #3007