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

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

4 new commits in sqlalchemy:

https://bitbucket.org/zzzeek/sqlalchemy/commits/3f85deb1b3f0/
Changeset:   3f85deb1b3f0
Branch:      None
User:        zzzeek
Date:        2013-07-02 18:56:20
Summary:     - add execution options/events tests

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/797acf8e1221/
Changeset:   797acf8e1221
Branch:      None
User:        zzzeek
Date:        2013-07-02 19:06:44
Summary:     - some more mocks

Affected #:  1 file

https://bitbucket.org/zzzeek/sqlalchemy/commits/e505db163745/
Changeset:   e505db163745
Branch:      ticket_2770
User:        zzzeek
Date:        2013-07-02 19:11:49
Summary:     changelog and some doc tweaks

Affected #:  2 files

https://bitbucket.org/zzzeek/sqlalchemy/commits/d3d10c982c8a/
Changeset:   d3d10c982c8a
Branch:      master
User:        zzzeek
Date:        2013-07-02 19:14:21
Summary:     - refactor pool a bit so that intent between ConnectionRecord/ConnectionFairy is clear;
make sure that the DBAPI connection passed to the reset-on-return events/dialect hooks
is also a "fairy", so that dictionaries like "info" are available.  [ticket:2770]
- rework the execution_options system so that the dialect is given the job of making
any immediate adjustments based on a set event.  move the "isolation level" logic to use
this new system.   Also work things out so that even engine-level execution options
can be used for things like isolation level; the dialect attaches a connect-event
handler in this case to handle the task.
- to support this new system as well as further extensibiltiy of execution options
add events engine_connect(), set_connection_execution_options(), set_engine_execution_options()

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