delta/python-packages/sqlalchemy.git/lib/sqlalchemy/sql, branch pr/129

- don't add the parent attach event within _on_table_attach

2014-08-15T18:27:12+00:00

if we already have a table; this prevents reentrant calls and
we aren't supporting columns/etc being moved around between different parents

- The ``info`` parameter has been added to the constructor for

2014-08-13T23:45:34+00:00

:class:`.SynonymProperty` and :class:`.ComparableProperty`.
- The ``info`` parameter has been added as a constructor argument
to all schema constructs including :class:`.MetaData`,
:class:`.Index`, :class:`.ForeignKey`, :class:`.ForeignKeyConstraint`,
:class:`.UniqueConstraint`, :class:`.PrimaryKeyConstraint`,
:class:`.CheckConstraint`.

fixes #2963

- rework documentation for reflection flags; also include

2014-08-09T22:08:05+00:00

information regarding #3027.

Providing an autoload_with info automatically sets autoload to True

2014-08-09T19:43:32+00:00

- Fixed bug in CTE where ``literal_binds`` compiler argument would not

2014-08-02T18:42:57+00:00

be always be correctly propagated when one CTE referred to another
aliased CTE in a statement.
Fixes #3154

- Fixed 0.9.7 regression caused by :ticket:`3067` in conjunction with

2014-07-29T17:32:05+00:00

a mis-named unit test such that so-called "schema" types like
:class:`.Boolean` and :class:`.Enum` could no longer be pickled.
fixes #3144

- Added a supported :meth:`.FunctionElement.alias` method to functions,

2014-07-24T18:33:50+00:00

e.g. the ``func`` construct.  Previously, behavior for this method
was undefined.  The current behavior mimics that of pre-0.9.4,
which is that the function is turned into a single-column FROM
clause with the given alias name, where the column itself is
anonymously named.
fixes #3137

- apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,

2014-07-20T16:44:40+00:00

sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing

- Fixed a SQLite join rewriting issue where a subquery that is embedded

2014-07-15T16:25:38+00:00

as a scalar subquery such as within an IN would receive inappropriate
substitutions from the enclosing query, if the same table were present
inside the subquery as were in the enclosing query such as in a
joined inheritance scenario.
fixes #3130

- wrestle with conv() and tests some more

2014-07-15T02:44:33+00:00