[Sqlalchemy-commits] commit/sqlalchemy: 3 new changesets

[Bitbucket <com...@bi...>]

3 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/bf67069d264c/
Changeset:   bf67069d264c
Branch:      None
User:        zzzeek
Date:        2014-02-26 19:28:14
Summary:     - Fixed issue in new :meth:`.TextClause.columns` method where the ordering
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.

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/302ad6228a12/
Changeset:   302ad6228a12
Branch:      None
User:        zzzeek
Date:        2014-02-26 21:34:49
Summary:     - Some changes to how the :attr:`.FromClause.c` collection behaves
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

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/6aeec027a0fb/
Changeset:   6aeec027a0fb
Branch:      None
User:        zzzeek
Date:        2014-02-26 21:45:52
Summary:     - Adjusted the logic which applies names to the .c collection when
a no-name :class:`.BindParameter` is received, e.g. via :func:`.sql.literal`
or similar; the "key" of the bind param is used as the key within
.c. rather than the rendered name.  Since these binds have "anonymous"
names in any case, this allows individual bound parameters to
have their own name within a selectable if they are otherwise unlabeled.
fixes #2974

Affected #:  4 files

Repository URL: https://bitbucket.org/zzzeek/sqlalchemy/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.