[ZODB-Dev] [Bug] Temporary connections go into "pool" on "close"

[Dieter Maurer]

ZODB 3.1, Python 2.1.3

When a temporary ZODB Connection is closed, it
is moved to the pool provided the pool contained already an entry
for the respective version.

This has two (potentially) nasty effects:

  *  we can get an unbounded number of connections in the
     pool (as temporary connections are not restricted in number
     and on close they become pool connections)

  *  when a temporary connection is closed and the associated
     transaction is not aborted/committed, the connections cache
     is in an indeterminate state.
     This would not be a problem when the connection were
     deleted (as "temporary" suggests). It may be a problem
     when the connection is reused as a pool connection.

-- 
Dieter