]> git.ipfire.org Git - thirdparty/sqlalchemy/sqlalchemy.git/commit
- Pool classes will reuse the same "pool_logging_name" setting
authorMike Bayer <mike_mp@zzzcomputing.com>
Mon, 31 May 2010 00:24:08 +0000 (20:24 -0400)
committerMike Bayer <mike_mp@zzzcomputing.com>
Mon, 31 May 2010 00:24:08 +0000 (20:24 -0400)
commit9bab63b69341bf9d89a30de2f624644b55afc6e9
treeb1c0a4956a743ba208a0c2cf506b9fcc634ac82d
parenta19e403010804ad25260a96e5f38e0894c1d72af
- Pool classes will reuse the same "pool_logging_name" setting
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.
CHANGES
lib/sqlalchemy/engine/__init__.py
lib/sqlalchemy/engine/base.py
lib/sqlalchemy/engine/threadlocal.py
lib/sqlalchemy/orm/mapper.py
lib/sqlalchemy/orm/query.py
lib/sqlalchemy/orm/session.py
lib/sqlalchemy/pool.py
test/aaa_profiling/test_memusage.py
test/aaa_profiling/test_zoomark_orm.py
test/engine/test_execute.py