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

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

6 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/dbd77e826b84/
Changeset:   dbd77e826b84
Branch:      None
User:        zzzeek
Date:        2014-07-04 03:49:10
Summary:     - Added new attributes :attr:`.ExecutionContext.exception` and
:attr:`.ExecutionContext.is_disconnect` which are meaningful within
the :meth:`.ConnectionEvents.dbapi_error` handler to see both the
original DBAPI error as well as whether or not it represents
a disconnect.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/c60eb86a91ea/
Changeset:   c60eb86a91ea
Branch:      None
User:        zzzeek
Date:        2014-07-04 03:49:37
Summary:     - Added new attributes :attr:`.ExecutionContext.exception` and
:attr:`.ExecutionContext.is_disconnect` which are meaningful within
the :meth:`.ConnectionEvents.dbapi_error` handler to see both the
original DBAPI error as well as whether or not it represents
a disconnect.

Affected #:  3 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/643a496d74c0/
Changeset:   643a496d74c0
Branch:      None
User:        Angus Lees
Date:        2014-07-04 10:06:34
Summary:     Tell mysql that Unicode columns are actually unicode.

Without this patch, Unicode columns get no special treatment by default,
and fall back to whatever the table, database, server configuration
and (eventually) server hardcoded default encoding is.  The hardcoded
default mysql encoding is latin1.

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/1c5ace0af482/
Changeset:   1c5ace0af482
Branch:      t
User:        zzzeek
Date:        2014-07-04 17:33:59
Summary:     Merge branch 'mysql-unicode' of https://github.com/anguslees/sqlalchemy into t

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/dfb5707dae45/
Changeset:   dfb5707dae45
Branch:      None
User:        zzzeek
Date:        2014-07-04 21:40:47
Summary:     - rework the entire approach to #3076. As we need to catch all exceptions
in all cases unconditionally, the number of use cases that go beyond what
dbapi_error() is expecting has gone too far for an 0.9 release.
Additionally, the number of things we'd like to track is really a lot
more than the five arguments here, and ExecutionContext is really not
suitable as totally public API for this.   So restore dbapi_error
to its old version, deprecate, and build out handle_error instead.
This is a lot more extensible and doesn't get in the way of anything
compatibility-wise.

Affected #:  8 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/946b92fcf9da/
Changeset:   946b92fcf9da
Branch:      rel_0_9
User:        zzzeek
Date:        2014-07-04 21:43:12
Summary:     - rework the entire approach to #3076. As we need to catch all exceptions
in all cases unconditionally, the number of use cases that go beyond what
dbapi_error() is expecting has gone too far for an 0.9 release.
Additionally, the number of things we'd like to track is really a lot
more than the five arguments here, and ExecutionContext is really not
suitable as totally public API for this.   So restore dbapi_error
to its old version, deprecate, and build out handle_error instead.
This is a lot more extensible and doesn't get in the way of anything
compatibility-wise.

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