delta/python-packages/sqlalchemy.git/lib/sqlalchemy/engine/strategies.py, branch pr/140

PEP8 style fixes

2014-07-14T00:10:55+00:00

- break up the copyright comment as part of a pass

2014-07-09T22:26:55+00:00

to get all flake8 passing

- vastly improve the "safe close cursor" tests in test_reconnect

2014-05-30T20:24:38+00:00

- Fixed bug which would occur if a DBAPI exception
occurs when the engine first connects and does its initial checks,
and the exception is not a disconnect exception, yet the cursor
raises an error when we try to close it.  In this case the real
exception would be quashed as we tried to log the cursor close
exception via the connection pool and failed, as we were trying
to access the pool's logger in a way that is inappropriate
in this very specific scenario. fixes #3063

- Added a new keyword argument ``once=True`` to :func:`.event.listen`

2014-03-11T16:27:10+00:00

and :func:`.event.listens_for`.  This is a convenience feature which
will wrap the given listener such that it is only invoked once.

- happy new year

2014-01-05T21:57:05+00:00

- The :func:`.engine_from_config` function has been improved so that

2013-12-07T23:38:15+00:00

we will be able to parse dialect-specific arguments from string
configuration dictionaries.  Dialect classes can now provide their
own list of parameter types and string-conversion routines.
The feature is not yet used by the built-in dialects, however.
[ticket:2875]

- A DBAPI that raises an error on ``connect()`` which is not a subclass

2013-12-07T22:20:05+00:00

of dbapi.Error (such as ``TypeError``, ``NotImplementedError``, etc.)
will propagate the exception unchanged.  Previously,
the error handling specific to the ``connect()`` routine would both
inappropriately run the exception through the dialect's
:meth:`.Dialect.is_disconnect` routine as well as wrap it in
a :class:`sqlalchemy.exc.DBAPIError`.  It is now propagated unchanged
in the same way as occurs within the execute process. [ticket:2881]
- add tests for this in test_parseconnect, but also add tests in test_execute
to ensure the execute() behavior as well

Dialect.initialize() is not called a second time if an :class:`.Engine`

2013-07-11T19:15:09+00:00

is recreated, due to a disconnect error.   This fixes a particular
issue in the Oracle 8 dialect, but in general the dialect.initialize()
phase should only be once per dialect.  Also in 0.8.3. [ticket:2776]

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

import of "sqlalchemy" and "sqlalchemy.orm" works.

2013-04-28T00:58:13+00:00