delta/python-packages/sqlalchemy.git/test/sql/test_selectable.py, branch pr/94

- Fixed bug in SQLite join rewriting where anonymized column names

2014-05-25T15:32:36+00:00

due to repeats would not correctly be rewritten in subqueries.
This would affect SELECT queries with any kind of subquery + join.
fixes #3057

Fix many typos throughout the codebase

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

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

- add further coverage for join_condition to make sure we get this case where

2014-03-28T20:41:08+00:00

there are multiple, equivalent foreign keys

- Some changes to how the :attr:`.FromClause.c` collection behaves

2014-02-26T20:34:49+00:00

when presented with duplicate columns.  The behavior of emitting a
warning and replacing the old column with the same name still
remains to some degree; the replacement in particular is to maintain
backwards compatibility.  However, the replaced column still remains
associated with the ``c`` collection now in a collection ``._all_columns``,
which is used by constructs such as aliases and unions, to deal with
the set of columns in ``c`` more towards what is actually in the
list of columns rather than the unique set of key names.  This helps
with situations where SELECT statements with same-named columns
are used in unions and such, so that the union can match the columns
up positionally and also there's some chance of :meth:`.FromClause.corresponding_column`
still being usable here (it can now return a column that is only
in selectable.c._all_columns and not otherwise named).
The new collection is underscored as we still need to decide where this
list might end up.   Theoretically it
would become the result of iter(selectable.c), however this would mean
that the length of the iteration would no longer match the length of
keys(), and that behavior needs to be checked out.
fixes #2974
- add a bunch more tests for ColumnCollection

- Fixed issue in new :meth:`.TextClause.columns` method where the ordering

2014-02-26T18:28:14+00:00

of columns given positionally would not be preserved.   This could
have potential impact in positional situations such as applying the
resulting :class:`.TextAsFrom` object to a union.

- for TextAsFrom, put the "inner" columns in the result map directly.

2014-02-11T00:17:00+00:00

Have also considered linking column.label() to the "column" itself being
in the result map but this reveals some naming collision problems (that
also seem to be very poorly tested...).   This should be as far as
we want to go right now with [ticket:2932].

- Fixed an 0.9 regression where the automatic aliasing applied by

2014-01-23T19:49:04+00:00

:class:`.Query` and in other situations where selects or joins
were aliased (such as joined table inheritance) could fail if a
user-defined :class:`.Column` subclass were used in the expression.
In this case, the subclass would fail to propagate ORM-specific
"annotations" along needed by the adaptation.  The "expression
annotations" system has been corrected to account for this case.
[ticket:2918]

- add support for specifying tables or entities for "of"

2013-11-29T04:23:27+00:00

- implement Query with_for_update()
- rework docs and tests

- fix up rendering of "of"

2013-11-29T03:25:09+00:00

- move out tests, dialect specific out of compiler, compiler tests use new API,
legacy API tests in test_selecatble
- add support for adaptation of ForUpdateArg, alias support in compilers

A :func:`.select` that is made to refer to itself in its FROM clause,

2013-10-09T00:06:58+00:00

typically via in-place mutation, will raise an informative error
message rather than causing a recursion overflow.
[ticket:2815]