summaryrefslogtreecommitdiff
path: root/test/engine/test_pool.py
Commit message (Collapse)AuthorAgeFilesLines
* - Removed some now unneeded version checks [ticket:2829] courtesy alex gaynorMike Bayer2013-09-221-1/+0
|
* try seeing if just clearing this ahead of time helpsMike Bayer2013-07-271-0/+1
|
* further tweakingMike Bayer2013-07-131-3/+2
|
* fix the scoping hereMike Bayer2013-07-131-2/+4
|
* Fixed bug where :class:`.QueuePool` would lose the correctMike Bayer2013-07-041-1/+50
| | | | | | checked out count if an existing pooled connection failed to reconnect after an invalidate or recycle event. Also in 0.8.3. [ticket:2772]
* - refactor pool a bit so that intent between ↵Mike Bayer2013-07-021-3/+4
| | | | | | | | | | | | | | ConnectionRecord/ConnectionFairy is clear; 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()
* mark the tests that seem to be segfauling py3k+coverage so that we can ↵Mike Bayer2013-06-301-0/+7
| | | | | | exclude them at the nose command line
* - replace most explicitly-named test objects called "Mock..." withMike Bayer2013-06-301-64/+85
| | | | | | | | | | | | 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.
* Preserve reset_on_return when recreating a Pool.pr/6Eevee2013-06-101-1/+2
|
* merge defaultMike Bayer2013-05-051-17/+20
|\
| * - cleanupMike Bayer2013-05-051-17/+20
| | | | | | | | - move the timeout here to 14 seconds as jenkins still chokes occasionally
* | - the raw 2to3 runMike Bayer2013-04-271-15/+15
|/ | | | - went through examples/ and cleaned out excess list() calls
* - recognize that do_rollback() and do_commit() work with a DBAPI connection,Mike Bayer2012-11-221-5/+73
| | | | | | | | | | | | | | | | | | whereas the other do_rollback_twophase(), savepoint etc. work with :class:`.Connection`. the context on these are different as twophase/savepoint are available at the :class:`.Connection` level, whereas commit/rollback are needed at a lower level as well. Rename the argument to "dbapi_connection" when the conneciton is in fact the DBAPI interface. - start thinking about being able to track "autocommit" vs. "commit", but not sure we have a need for this yet. - have Pool call out to a Dialect for all rollback/commit/close operations now. Pool no longer calls DBAPI methods directly. May use this for a workaround for [ticket:2611] - add a new Pool event reset() to allow the pool's reset of the connection to be intercepted. - remove methods in Informix dialect which appear to be hardcoding some isolation settings on new Transaction only; the isolation API should be implemented for Informix. also removed "flag" for transaction commit/rollback being not available; this should be based on server/DBAPI version and we will need someone with test access in order to help determine how this should work
* trying different approaches to test layout. in this one, the testing modulesMike Bayer2012-09-271-5/+5
| | | | | | | become an externally usable package but still remains within the main sqlalchemy parent package. in this system, we use kind of an ugly hack to get the noseplugin imported outside of the "sqlalchemy" package, while still making it available within sqlalchemy for usage by third party libraries.
* - add req's for predictable gcMike Bayer2012-09-051-0/+2
|
* - [feature] Added support for .info dictionary argument toMike Bayer2012-08-241-1/+1
| | | | | | column_property(), relationship(), composite(). All MapperProperty classes have an auto-creating .info dict available overall.
* try to loosen the times up here to reduce failures due to latencyMike Bayer2012-07-171-18/+18
|
* notify_all workaround for 2.5Mike Bayer2012-06-251-0/+1
|
* - change notify to notify_all() so all waiters exit immediately,Mike Bayer2012-06-251-6/+39
| | | | continuing [ticket:2522]
* - [bug] Fixed bug wherebyMike Bayer2012-06-221-0/+63
| | | | | | | | | | | | a disconnect detect + dispose that occurs when the QueuePool has threads waiting for connections would leave those threads waiting for the duration of the timeout on the old pool. The fix now notifies those waiters with a special exception case and has them move onto the new pool. This fix may or may not be ported to 0.7. [ticket:2522]
* ensure sa_pool_key isn't passed to connectMike Bayer2011-09-211-0/+15
|
* - The recreate() method in all pool classes usesMike Bayer2011-08-141-1/+2
| | | | | | | self.__class__ to get at the type of pool to produce, in the case of subclassing. Note there's no usual need to subclass pools. [ticket:2254]
* - hardcore force every connection into a strong-referenced set, rollback on ↵Mike Bayer2011-04-251-3/+4
| | | | | | | | | every test, close on every context. this uses pool events but bypasses the pool's fairy/record/dispose services. pypy still seems to expose some holes in that at least as far as what some (or maybe just one, cant find it yet) of the tests does. haven't tested this too deeply, just on sqlite + postgres, cypthon 2.7 + pypy. will see what the buildbot says
* - The "pool.manage" feature doesn't use pickleMike Bayer2011-04-051-14/+15
| | | | anymore to hash the arguments for each pool.
* - remove test.sql._base, test.engine._base, test.orm._base, move those ↵Mike Bayer2011-03-271-2/+3
| | | | | | | classes to a new test.lib.fixtures module - move testing.TestBase to test.lib.fixtures - massive search and replace
* - Fixed bug in QueuePool, SingletonThreadPool wherebyMike Bayer2011-03-221-1/+47
| | | | | | | | | connections that were discarded via overflow or periodic cleanup() were not explicitly closed, leaving garbage collection to the task instead. This generally only affects non-reference-counting backends like Jython and Pypy. Thanks to Jaimy Azle for spotting this. [ticket:2102]
* - Fixed AssertionPool regression bug. A replacement of finalizeMike Bayer2011-03-161-1/+19
| | | | | | logic did the wrong thing, but then also the logic it replaced also doesn't seem like its needed. If it is, would rather have a test case first so its out for now, added tests for assertionpool. [ticket:2097]
* - whitespace removal bonanzaMike Bayer2011-01-021-47/+47
|
* - removes the "on_" prefix.Mike Bayer2010-12-301-28/+28
|
* - they don't want "on_". First step, change the naming convention on EventsMike Bayer2010-12-301-1/+1
| | | | so that non-events are just _name.
* new calling style: event.listen(target, identifier, fn)Mike Bayer2010-12-011-11/+11
|
* - sqlalchemy.test and nose plugin moves back to being entirelyMike Bayer2010-11-281-3/+3
|\ | | | | | | | | | | | | | | | | | | | | | | outside of "sqlalchemy" and under "test/". Rationale: - coverage plugin works without issue, without need for an awkward additional package install - command line for "nosetests" isn't polluted with SQLAlchemy options [ticket:1949]
| * - move sqlalchemy.test to test.libMike Bayer2010-11-151-3/+3
| |
* | - SessionEvents is on board and the event model is done, can start building ↵Mike Bayer2010-11-141-2/+32
| | | | | | | | 0.7 tip soon
* | - pool event tests that don't depend on deprecated listener system,Mike Bayer2010-11-141-101/+228
| | | | | | | | | | attempting "test just one thing" style - reorganize fixtures to come primarily from the base test class
* | - basic docsMike Bayer2010-11-091-0/+30
| | | | | | | | - poolevent accepts Engine as a target
* | dingMike Bayer2010-11-071-3/+3
| |
* | merge tipMike Bayer2010-10-021-1/+1
|\ \ | |/
| * - *Major* cleanup / modernization of the InformixMike Bayer2010-10-011-1/+1
| | | | | | | | | | dialect for 0.6, courtesy Florian Apolloner. [ticket:1906]
* | merge from tipMike Bayer2010-09-031-1/+1
|\ \ | |/
| * - replaced all self.__connection.is_valid withMike Bayer2010-08-261-1/+1
| | | | | | | | | | | | | | | | | | | | | | "safe" self._connection_is_valid. - Fixed bug in Connection whereby if a "disconnect" event occurred in the "initialize" phase of the first connection pool connect, an AttributeError would be raised when the Connection would attempt to invalidate the DBAPI connection. [ticket:1894] - Connection.invalidate() can be called more than once and subsequent calls do nothing.
* | - reorganize events into cls->dispatch, which is an instance of _Dispatch.Mike Bayer2010-08-101-7/+7
| | | | | | | | | | | | cut down on extraneous stuff, cleanup The Event class never gets instantiated and its methods stay the same so that sphinx can get to it.
* | working with how this will be documented and having some probs with sphinxMike Bayer2010-08-091-4/+4
| |
* | - pretty much all tests passing, maybe some callcounts are offMike Bayer2010-07-251-13/+12
|/ | | | | - test suite adjusted to use engine/pool events and not listeners - deprecation warnings
* Python-tidy test/engine and test/aaa_profiling, 80% auto + 20% manual ↵Mike Bayer2010-07-111-74/+84
| | | | intervention
* - StaticPool now initializes, disposes and recreates withoutMike Bayer2010-03-191-0/+19
| | | | | | opening a new connection - the connection is only opened when first requested. dispose() also works on AssertionPool now. [ticket:1728]
* fix the timeout test once and for allMike Bayer2010-03-131-4/+5
|
* fix last commitPhilip Jenvey2010-03-081-1/+1
|
* small cleanupPhilip Jenvey2010-03-081-1/+1
|
* there we go, that was the stupid gc bugMike Bayer2010-03-011-0/+2
|
View Lorry Controller Status