delta/python-packages/sqlalchemy.git/test/engine, branch pr/146

- control the module name of the exception here for py3k compat

2014-10-19T17:37:48+00:00

- Exception messages have been spiffed up a bit. The SQL statement

2014-10-17T23:37:45+00:00

and parameters are not displayed if None, reducing confusion for
error messages that weren't related to a statement.  The full
module and classname for the DBAPI-level exception is displayed,
making it clear that this is a wrapped DBAPI exception.  The
statement and parameters themselves are bounded within a bracketed
sections to better isolate them from the error message and from
each other.
fixes #3172

- adjustment for ref #3200 as we need an immutabledict() here so

2014-10-07T16:43:27+00:00

that union() can be called, in the case of a dialect that uses
execution options inside of initialize() (e.g. oursql)

- The execution options passed to an :class:`.Engine` either via

2014-10-06T22:23:42+00:00

:paramref:`.create_engine.execution_options` or
:meth:`.Engine.update_execution_options` are not passed to the
special :class:`.Connection` used to initialize the dialect
within the "first connect" event; dialects will usually
perform their own queries in this phase, and none of the
current available  options should be applied here.  In
particular, the "autocommit" option was causing an attempt to
autocommit within this initial connect which would fail with
an AttributeError due to the non-standard state of the
:class:`.Connection`.
fixes #3200

- repair autorollback for branches

2014-09-27T01:41:15+00:00

- Fixed bug where a "branched" connection, that is the kind you get

2014-09-26T20:25:26+00:00

when you call :meth:`.Connection.connect`, would not share transaction
status with the parent.  The architecture of branching has been tweaked
a bit so that the branched connection defers to the parent for
all transactional status and operations.
fixes #3190

- Fixed bug where a "branched" connection, that is the kind you get

2014-09-26T18:55:36+00:00

when you call :meth:`.Connection.connect`, would not share invalidation
status with the parent.  The architecture of branching has been tweaked
a bit so that the branched connection defers to the parent for
all invalidation status and operations.
fixes #3215

- these tests don't test anything in SQLAlchemy - from our perpsective,

2014-09-19T16:41:07+00:00

we need to be in transactions (tested elsewhere) and we need to
emit the correct FOR UPDATE strings (tested elsewhere).  There's nothing
in SQLA to be tested as far as validating that for update causes exceptions
or not, and these tests frequently fail as they are timing sensitive.

- Fixed bug that affected generally the same classes of event

2014-09-18T21:49:07+00:00

as that of :ticket:`3199`, when the ``named=True`` parameter
would be used.  Some events would fail to register, and others
would not invoke the event arguments correctly, generally in the
case of when an event was "wrapped" for adaption in some other way.
The "named" mechanics have been rearranged to not interfere with
the argument signature expected by internal wrapper functions.
fixes #3197

- An adjustment to table/index reflection such that if an index

2014-09-02T18:18:09+00:00

reports a column that isn't found to be present in the table,
a warning is emitted and the column is skipped.  This can occur
for some special system column situations as has been observed
with Oracle. fixes #3180