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

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

4 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/356d6659b17d/
Changeset:   356d6659b17d
Branch:      None
User:        zzzeek
Date:        2014-09-05 22:28:20
Summary:     - tiny refactors #1-#5

Affected #:  4 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/583287259fbb/
Changeset:   583287259fbb
Branch:      None
User:        zzzeek
Date:        2014-09-05 22:28:32
Summary:     - delete the file first here so this is deterministic

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/d39daa43fe79/
Changeset:   d39daa43fe79
Branch:      ticket_3100
User:        zzzeek
Date:        2014-09-05 22:29:08
Summary:     Merge branch 'master' into ticket_3100

Affected #:  5 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/7b766591b05c/
Changeset:   7b766591b05c
Branch:      None
User:        zzzeek
Date:        2014-09-05 22:44:42
Summary:     - MySQL boolean symbols "true", "false" work again.  0.9's change
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

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.