delta/python-packages/sqlalchemy.git/lib/sqlalchemy, branch ticket_3148

- rework ColumnAdapter and ORMAdapter to only provide the features

2014-09-07T18:55:44+00:00

we're now using; rework them fully so that their behavioral contract
is consistent regarding adapter.traverse() vs. adapter.columns[],
add a full suite of tests including advanced wrapping scenarios
previously only covered by test/orm/test_froms.py and
test/orm/inheritance/test_relationships.py
- identify several cases where label._order_by_label_clause would be
corrupted, e.g. due to adaption or annotation separately
- add full tests for #3148

- enhance ClauseAdapter / ColumnAdapter to have new behaviors with labels.

2014-09-07T04:01:34+00:00

The "anonymize label" logic is now generalized to ClauseAdapter, and takes
place when the anonymize_labels flag is sent, taking effect for all
.columns lookups as well as within traverse() calls against the label
directly.
- traverse() will also memoize what it gets in columns, so that
calling upon traverse() / .columns against the same Label will
produce the same anonymized label.  This is so that AliasedClass
produces the same anonymized label when it is accessed per-column
(e.g. SomeAlias.some_column) as well as when it is applied to a Query,
and within column loader strategies (e.g. query(SomeAlias)); the
former uses traverse() while the latter uses .columns
- AliasedClass now calls onto ColumnAdapter
- Query also makes sure to use that same ColumnAdapter from the AliasedClass
in all cases
- update the logic from 0.9 in #1068 to make use of the same
_label_resolve_dict we use for #2992, simplifying how that works
and adding support for new scenarios that were pretty broken
(see #3148, #3188)

wip for #3148

2014-09-06T21:56:53+00:00

- document all the varities of _label on the base ColumnElement

2014-09-06T20:20:01+00:00

- replace out _columns_clause_label with a straight boolean flag to
reduce the proliferation of labels

- omit MySQL index flavor if its None

2014-09-05T21:02:33+00:00

- MySQL boolean symbols "true", "false" work again. 0.9's change

2014-09-05T20:44:42+00:00

in :ticket:`2682` disallowed the MySQL dialect from making use of the
"true" and "false" symbols in the context of "IS" / "IS NOT", but
MySQL supports this syntax even though it has no boolean type.
MySQL remains "non native boolean", but the :func:`.true`
and :func:`.false` symbols again produce the
keywords "true" and "false", so that an expression like
``column.is_(true())`` again works on MySQL.
fixes #3186

- tiny refactors #1-#5

2014-09-05T20:28:20+00:00

- ensure literal_binds works with LIMIT clause, FOR UPDATE

2014-09-03T23:42:38+00:00

- The hostname-based connection format for SQL Server when using

2014-09-03T14:31:29+00:00

pyodbc will no longer specify a default "driver name", and a warning
is emitted if this is missing.  The optimal driver name for SQL Server
changes frequently and is per-platform, so hostname based connections
need to specify this. DSN-based connections are preferred.
fixes #3182

- An adjustment to table/index reflection such that if an index

2014-09-02T18:18:09+00:00

reports a column that isn't found to be present in the table,
a warning is emitted and the column is skipped.  This can occur
for some special system column situations as has been observed
with Oracle. fixes #3180