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

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

4 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/cc29c4afff20/
Changeset:   cc29c4afff20
Branch:      None
User:        zzzeek
Date:        2014-10-11 22:25:21+00:00
Summary:     - Fixed long-standing bug in Oracle dialect where bound parameter
names that started with numbers would not be quoted, as Oracle
doesn't like numerics in bound parameter names.
fixes #2138

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d2997166ee07/
Changeset:   d2997166ee07
Branch:      None
User:        zzzeek
Date:        2014-10-11 22:25:54+00:00
Summary:     - Fixed long-standing bug in Oracle dialect where bound parameter
names that started with numbers would not be quoted, as Oracle
doesn't like numerics in bound parameter names.
fixes #2138

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/83e465633793/
Changeset:   83e465633793
Branch:      None
User:        zzzeek
Date:        2014-10-11 22:35:12+00:00
Summary:     - embedding an existing predicate into a new one only
seems to be used by test_oracle->test_coerce_to_unicode().  The
predicate here should treat as a lambda based on enabled_for_config.
not sure why this test is not failing on jenkins

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/19b375579e65/
Changeset:   19b375579e65
Branch:      rel_0_9
User:        zzzeek
Date:        2014-10-11 22:36:04+00:00
Summary:     - embedding an existing predicate into a new one only
seems to be used by test_oracle->test_coerce_to_unicode().  The
predicate here should treat as a lambda based on enabled_for_config.
not sure why this test is not failing on jenkins

Affected #:  1 file

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.