delta/python-packages/sqlalchemy.git/test/engine/test_execute.py, branch pr/17

- refactor pool a bit so that intent between ConnectionRecord/ConnectionFairy is clear;

2013-07-02T17:14:21+00:00

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()

- replace most explicitly-named test objects called "Mock..." with

2013-06-30T22:35:12+00:00

actual mock objects from the mock library.  I'd like to use mock
for new tests so we might as well use it in obvious places.
- use unittest.mock in py3.3
- changelog
- add a note to README.unittests
- add tests_require in setup.py
- have tests import from sqlalchemy.testing.mock
- apply usage of mock to one of the event tests.  we can be using
this approach all over the place.

fix test_execute w c extensions

2013-05-27T00:44:34+00:00

test_execute up for sqlite, pg, oursql, mysql 2.7 + 3.3

2013-05-04T19:29:04+00:00

- the raw 2to3 run

2013-04-27T23:53:57+00:00

- went through examples/ and cleaned out excess list() calls

Merged in nakagami/sqlalchemy/cymysql (pull request #42)

2013-03-07T17:36:35+00:00

cymysql support

- Fixed an import of "logging" in test_execute which was not

2013-03-02T21:20:49+00:00

working on some linux platforms.  Also in 0.7.11.
- only need "logging.handlers" here, "logging" comes in implicitly

test_execute: import logging.handlers to fix AttributeError

2013-02-27T20:01:37+00:00

See also: https://bugs.gentoo.org/show_bug.cgi?id=458684

test for cymysql

2013-02-17T06:07:19+00:00

Added a new method :meth:`.Engine.execution_options`

2012-10-23T16:08:20+00:00

      to :class:`.Engine`.  This method works similarly to
      :class:`.Connection.execution_options` in that it creates
      a copy of the parent object which will refer to the new
      set of options.   The method can be used to build
      sharding schemes where each engine shares the same
      underlying pool of connections.   The method
      has been tested against the horizontal shard
      recipe in the ORM as well.