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

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

16 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/eb4abda81172/
Changeset:   eb4abda81172
Branch:      None
User:        zzzeek
Date:        2014-07-15 00:28:07
Summary:     - Fixed bug where multi-valued :class:`.Insert` construct would fail
to check subsequent values entries beyond the first one given
for literal SQL expressions.
fixes #3069

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/6fad9651b722/
Changeset:   6fad9651b722
Branch:      None
User:        zzzeek
Date:        2014-07-15 00:28:23
Summary:     - Fixed bug where multi-valued :class:`.Insert` construct would fail
to check subsequent values entries beyond the first one given
for literal SQL expressions.
fixes #3069

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/461993641704/
Changeset:   461993641704
Branch:      None
User:        zzzeek
Date:        2014-07-15 00:34:32
Summary:      -Fixed bug in common table expressions whereby positional bound
parameters could be expressed in the wrong final order
when CTEs were nested in certain ways.
fixes #3090

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/da46b015f075/
Changeset:   da46b015f075
Branch:      None
User:        zzzeek
Date:        2014-07-15 00:34:52
Summary:      -Fixed bug in common table expressions whereby positional bound
parameters could be expressed in the wrong final order
when CTEs were nested in certain ways.
fixes #3090

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/ec40a84d96e4/
Changeset:   ec40a84d96e4
Branch:      None
User:        zzzeek
Date:        2014-07-15 00:49:06
Summary:     - Fixed a regression from 0.9.0 due to :ticket:`2736` where the
:meth:`.Query.select_from` method no longer set up the "from
entity" of the :class:`.Query` object correctly, so that
subsequent :meth:`.Query.filter_by` or :meth:`.Query.join`
calls would fail to check the appropriate "from" entity when
searching for attributes by string name.
fixes #3083

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/87a4ebf8af84/
Changeset:   87a4ebf8af84
Branch:      None
User:        zzzeek
Date:        2014-07-15 00:49:32
Summary:     - Fixed a regression from 0.9.0 due to :ticket:`2736` where the
:meth:`.Query.select_from` method no longer set up the "from
entity" of the :class:`.Query` object correctly, so that
subsequent :meth:`.Query.filter_by` or :meth:`.Query.join`
calls would fail to check the appropriate "from" entity when
searching for attributes by string name.
fixes #3083

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/0add251ea0be/
Changeset:   0add251ea0be
Branch:      None
User:        zzzeek
Date:        2014-07-15 00:54:23
Summary:     - In the SQL Server pyodbc dialect, repaired the implementation
for the ``description_encoding`` dialect parameter, which when
not explicitly set was preventing  cursor.description from
being parsed correctly in the case of result sets that
contained names in alternate encodings.  This parameter
shouldn't be needed going forward.
fixes #3091

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/a1d9c81f5ac7/
Changeset:   a1d9c81f5ac7
Branch:      None
User:        zzzeek
Date:        2014-07-15 00:55:02
Summary:     - In the SQL Server pyodbc dialect, repaired the implementation
for the ``description_encoding`` dialect parameter, which when
not explicitly set was preventing  cursor.description from
being parsed correctly in the case of result sets that
contained names in alternate encodings.  This parameter
shouldn't be needed going forward.
fixes #3091

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/a81d3a23c005/
Changeset:   a81d3a23c005
Branch:      None
User:        zzzeek
Date:        2014-07-15 00:57:25
Summary:     - In the SQL Server pyodbc dialect, repaired the implementation
for the ``description_encoding`` dialect parameter, which when
not explicitly set was preventing  cursor.description from
being parsed correctly in the case of result sets that
contained names in alternate encodings.  This parameter
shouldn't be needed going forward.
fixes #3091

Conflicts:
	test/sql/test_unicode.py

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/2825730e7be6/
Changeset:   2825730e7be6
Branch:      None
User:        zzzeek
Date:        2014-07-15 01:02:20
Summary:     - Added statement encoding to the "SET IDENTITY_INSERT"
statements which operate when an explicit INSERT is being
interjected into an IDENTITY column, to support non-ascii table
identifiers on drivers such as pyodbc + unix + py2k that don't
support unicode statements.
ref #3091 as this fix is also in that issue's patch, but is
a different issue.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/1604b5c08917/
Changeset:   1604b5c08917
Branch:      None
User:        zzzeek
Date:        2014-07-15 01:03:40
Summary:     - Added statement encoding to the "SET IDENTITY_INSERT"
statements which operate when an explicit INSERT is being
interjected into an IDENTITY column, to support non-ascii table
identifiers on drivers such as pyodbc + unix + py2k that don't
support unicode statements.
ref #3091 as this fix is also in that issue's patch, but is
a different issue.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/74d38623ff52/
Changeset:   74d38623ff52
Branch:      rel_0_8
User:        zzzeek
Date:        2014-07-15 01:03:59
Summary:     - Added statement encoding to the "SET IDENTITY_INSERT"
statements which operate when an explicit INSERT is being
interjected into an IDENTITY column, to support non-ascii table
identifiers on drivers such as pyodbc + unix + py2k that don't
support unicode statements.
ref #3091 as this fix is also in that issue's patch, but is
a different issue.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/6fd0bc7c6284/
Changeset:   6fd0bc7c6284
Branch:      None
User:        zzzeek
Date:        2014-07-15 01:16:11
Summary:     - Fixed a regression from 0.9.5 caused by :ticket:`3025` where the
query used to determine "default schema" is invalid in SQL Server 2000.
For SQL Server 2000 we go back to defaulting to the "schema name"
parameter of the dialect, which is configurable but defaults
to 'dbo'. fixes #3025

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c9a59575ebfd/
Changeset:   c9a59575ebfd
Branch:      None
User:        zzzeek
Date:        2014-07-15 01:16:42
Summary:     - Fixed a regression from 0.9.5 caused by :ticket:`3025` where the
query used to determine "default schema" is invalid in SQL Server 2000.
For SQL Server 2000 we go back to defaulting to the "schema name"
parameter of the dialect, which is configurable but defaults
to 'dbo'. fixes #3025

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d2193f53c10d/
Changeset:   d2193f53c10d
Branch:      None
User:        zzzeek
Date:        2014-07-15 02:26:38
Summary:     - Fix bug in naming convention feature where using a check
constraint convention that includes ``constraint_name`` would
then force all :class:`.Boolean` and :class:`.Enum` types to
require names as well, as these implicitly create a
constraint, even if the ultimate target backend were one that does
not require generation of the constraint such as Postgresql.
The mechanics of naming conventions for these particular
constraints has been reorganized such that the naming
determination is done at DDL compile time, rather than at
constraint/table construction time.
fixes #3067

Affected #:  6 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d462dbde9976/
Changeset:   d462dbde9976
Branch:      rel_0_9
User:        zzzeek
Date:        2014-07-15 02:27:16
Summary:     - Fix bug in naming convention feature where using a check
constraint convention that includes ``constraint_name`` would
then force all :class:`.Boolean` and :class:`.Enum` types to
require names as well, as these implicitly create a
constraint, even if the ultimate target backend were one that does
not require generation of the constraint such as Postgresql.
The mechanics of naming conventions for these particular
constraints has been reorganized such that the naming
determination is done at DDL compile time, rather than at
constraint/table construction time.
fixes #3067

Affected #:  6 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.