delta/python-packages/sqlalchemy.git/test/ext, branch pr/210

- exclude this from unpredictable gc

2015-10-11T16:44:29+00:00

- Added the :paramref:`.AssociationProxy.info` parameter to the

2015-10-09T22:01:43+00:00

:class:`.AssociationProxy` constructor, to suit the
:attr:`.AssociationProxy.info` accessor that was added in
:ticket:`2971`.  This is possible because :class:`.AssociationProxy`
is constructed explicitly, unlike a hybrid which is constructed
implicitly via the decorator syntax.
fixes #3551

Merge remote-tracking branch 'origin/pr/203'

2015-10-09T21:11:56+00:00

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

Remplement Query.one() in terms of .one_or_none()

2015-09-28T16:08:19+00:00

Thanks to Mike Bayer for suggesting a simpler refactoring.

Fix sqlalchemy.ext.baked.Result.one_or_none() exception message

2015-09-24T19:25:15+00:00

Also add a couple of missing tests.

- replicate Query.one_or_none to BakedQuery

2015-09-24T17:52:25+00:00

- changelog / version note finishing

- 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 an unexpected-use regression whereby custom :class:`.Comparator`

2015-06-11T20:48:00+00:00

objects that made use of the ``__clause_element__()`` method and
returned an object that was an ORM-mapped
:class:`.InstrumentedAttribute` and not explicitly a
:class:`.ColumnElement` would fail to be correctly
handled when passed as an expression to :meth:`.Session.query`.
The logic in 0.9 happened to succeed on this, so this use case is now
supported. fixes #3448

- repair these tests to use the global manager_of_class fn,

2015-06-07T21:44:58+00:00

as test_customfinder_pass at least does not provide the
alternate ext manager and in all cases it's the global function
that counts