delta/python-packages/sqlalchemy.git/test/orm/test_composites.py, branch pr200

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

- Improved the initialization logic of composite attributes such that

2014-02-04T00:13:16+00:00

calling ``MyClass.attribute`` will not require that the configure
mappers step has occurred, e.g. it will just work without throwing
any error. [ticket:2935]

make the error message for [ticket:2889] more accurate, as we support

2013-12-12T18:36:58+00:00

composites to many-to-ones now also

- :func:`.composite` will raise an informative error message when the

2013-12-12T18:30:16+00:00

columns/attribute (names) passed don't resolve to a Column or mapped
attribute (such as an erroneous tuple); previously raised an unbound
local. [ticket:2889]

clean up imports

2013-11-23T22:12:54+00:00

- A new construct :class:`.Bundle` is added, which allows for specification

2013-10-03T21:06:55+00:00

of groups of column expressions to a :class:`.Query` construct.
The group of columns are returned as a single tuple by default.  The
behavior of :class:`.Bundle` can be overridden however to provide
any sort of result processing to the returned row.  One example included
is :attr:`.Composite.Comparator.bundle`, which applies a bundled form
of a "composite" mapped attribute.
[ticket:2824]
- The :func:`.composite` construct now maintains the return object
when used in a column-oriented :class:`.Query`, rather than expanding
out into individual columns.  This makes use of the new :class:`.Bundle`
feature internally.  This behavior is backwards incompatible; to
select from a composite column which will expand out, use
``MyClass.some_composite.clauses``.

Fixed bug where sending a composite attribute into :meth:`.Query.order_by`

2013-06-10T17:50:06+00:00

would produce a parenthesized expression not accepted by some databases.
[ticket:2754]

Fixed the interaction between composite attributes and

2013-06-10T17:45:19+00:00

the :func:`.aliased` function.  Previously, composite attributes
wouldn't work correctly in comparison operations when aliasing
was applied.  Also in 0.8.2. [ticket:2755]

- the raw 2to3 run

2013-04-27T23:53:57+00:00

- went through examples/ and cleaned out excess list() calls

trying different approaches to test layout. in this one, the testing modules

2012-09-27T06:37:33+00:00

become an externally usable package but still remains within the main sqlalchemy parent package.
in this system, we use kind of an ugly hack to get the noseplugin imported outside of the
"sqlalchemy" package, while still making it available within sqlalchemy for usage by
third party libraries.