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

-whitespace removal bonanza

2011-01-02T19:25:15+00:00

- and fix everything from the last checkin that breaks on py 2.4, 2.5

2010-11-09T16:46:52+00:00

- Implemented sequence check capability for the C

2010-11-09T16:40:23+00:00

version of RowProxy, as well as 2.7 style
"collections.Sequence" registration for RowProxy.
[ticket:1871]

- Major cleanup / modernization of the Informix

2010-10-02T01:26:05+00:00

dialect for 0.6, courtesy Florian Apolloner.
[ticket:1906]

Python-tidy test/engine and test/aaa_profiling, 80% auto + 20% manual intervention

2010-07-11T17:15:51+00:00

- Pool classes will reuse the same "pool_logging_name" setting

2010-05-31T00:24:08+00:00

after a dispose() occurs.

- Engine gains an "execution_options" argument and
update_execution_options() method, which will apply to
all connections generated by this engine.

- Added more aggressive caching to the mapper's usage of
UPDATE, INSERT, and DELETE expressions.  Assuming the
statement has no per-object SQL expressions attached,
the expression objects are cached by the mapper after
the first create, and their compiled form is stored
persistently in a cache dictionary for the duration of
the related Engine.

- change #3 required change #1 so that we could test
a set of mappers operating over the course of many engines without
memory usage increase.

further testing reveals that cursor.rowcount is only called with update/delete and DDL,

2010-04-13T00:20:50+00:00

and also that FB's cursor.rowcount is a little expensive, but not dramatically.
added a test to ensure cursor.rowcount is only called on update/delete.
the current default for firebird enable_rowcount is now True, leaving all the
options to turn it off etc..

- added a test for the solution in [ticket:1757].

2010-04-11T19:37:20+00:00

- this does imply that a lot of the "test the RowProxy" tests in sql/test_query might be better off in engine/test_execute or perhaps engine/test_resultproxy

fix this test for oracle

2010-04-08T00:25:37+00:00

- ah. oursql didn't have "extra steps" here, the previous system within execution_options()

2010-04-07T19:20:20+00:00

used by oursql would generate a proxied connection from within the dialect.initialize() phase.  the new
clone system bypasses that.