Package: repoze.zodbconn
A lbrary which allowsZODBdatabases to be
constructed from URI specifications.Read the latest documentation athttp://docs.repoze.org/zodbconn/.repoze.zodbconnChangelog0.15 (2013-07-22)Worked around broken stdliburlsplitimplementations  which jam
thefragmentfor non-standard URIs into the path.Add support for Python 3.2 / 3.3.0.14 (2012-03-16)Made compatible with ZODB 3.10.3.  The only change to non-testing code is
in the factory for demo and blob storage, the demo storage now wraps the
blob storage instead of the other way around as it was previously.Made sure therepoze.zodbconn.connectormiddleware calls the sub
application before returning an iterator.Reverted the change from 0.12 to eagerly open the database at startup time.
Changed to lazily opening the database but the accessor for the database is
now guarded by a lock in order to prevent the race condition being targed by
the change from 0.12.0.13 (2011-06-04)If a closer is already present in the environment, allow the finder
to use it’sim_selfas the connection, rather than opening a new
connection.Extendrepoze.zodbconn.connectormiddleware to support streaming
applications.  Thanks to Stephane Klein for the patch.New URI resolver type:memory://, which creates a
ZODB.MappingStorage.MappingStorage storage.0.12 (2010-06-25)PersistentApplicationFinder: More eagerly open the database at
startup time in order to avoid race condition where many
simultaneous requests directly after startup might cause the
database to be created more than once.0.11 (2010-04-26)Made the URI resolver compatible with changes to Python’surlparsemodule in Python 2.6.5 (tests all pass now on Python 2.4.6, 2.5.5,
and 2.6.5).  Thanks to Fergus Doyle for the patch.In the connector middleware, abort the transaction before closing
the connection, to avoid an exception that would lead to leaked
connections.The ZConfig file parser now allows a config file to define multiple
databases.0.10 (2009-06-24)Added azconfigURI parser, providing basic support for any
kind of storage that ZODB can load via ZConfig.Added adb_from_urifunction, which is simpler to use thandbfactory_from_uri;db_from_urialso supports
multi-databases.  Replaced references in the documentation.Addedconnector, a WSGI framework component that connects to ZODB
and puts the connection in the WSGI environment. It unconditionally
closes the ZODB connection on exit.PersistentApplicationFindernow gets the ZODB connection
from the WSGI environment whenever it is provided.Moveddb_from_urianddbfactory_from_urito a module
nameduri, to avoid circular imports.Addedcachecleanup, a WSGI framework component that keeps only
objects of certain classes in the ZODB cache. This helps control
memory consumption.Addedtransferlog, a WSGI framework component that logs
how many ZODB objects were loaded and stored per request.0.9.1 (2009-06-12)TheEnvironmentDeleterMiddleware(the “closer”) middleware did
not delete the environment key if the application raised an
exception, potentially causing connection leakage for applications
that depended upon it doing so.0.9 (2009-06-09)FeaturesAdded aLoggingCleanupimplementation which can be passed toPersistentApplicationFinder:  it logs counts of loaded and saved
objects for the connection between the time it is instantiated (i.e.,
whe the database connection is opened) and the time the connection is
closed.  See the “Customizing Connection Cleanup” section in the narrative
docs for notes on using this feature.Addedcleanupargument to constructor ofPersistentApplicationFinder,
to allow applications to register a custom cleanup object factory.
See the “Customizing Connection Cleanup” section in the narrative docs
for notes on using this feature.100% unit test coverage.Bug FixesFixed breakage withfile:URIs having no query string.0.8 (2009-05-25)FeaturesFix a bug in FileStorageURIResolver whereby fully-qualified paths to
Windows files (e.g.file://C:\foo\bar\baz?a=1) were parsed
incorrectly, resulting in a bogus file location.0.7 (2009-04-23)FeaturesAdded support for multi-databases in PersistentApplicationFinder.
Just pass multiple URIs to the constructor, either as a list of
strings or a single string with URIs separated by whitespace. Each
database must have a distinct database_name. The first URI specifies
the root database.0.6 (2008-01-06)Backwards Incompatibilitiesdbfactory_from_urinow returns only a single argument (the
factory).FeaturesDocs updated with argument values forfile://andzeo://URI
schemes; this file converted to real REST.0.5 (unknown)Passlayoutto BlobStorage as a kwarg explicitly (for forward
compatibility).Depend on ZODB3 3.8.1+.0.4 (unknown)Addconnection_cache_size,connection_pool_size, anddatabase_namearguments to both FileStorage and ClientStorage URI
resolver schemes.connection_cache_sizerepresents the ZODB
object cache size (thecache_sizeparameter to the DB
constructor),connection_pool_sizerepresents the ZODB connection
pool size (thepool_sizeparameter to the DB constructor), anddatabase_namerepresents the ZODB database name (thedatabase_nameparameter to the DB constructor).connection_cache_sizedefaults to 10000 (overriding the too-low DB
constructor default of 400),connection_pool_sizedefaults to 7,
anddatabase_namedefaults tounnamed.0.3 (unknown)Add ‘egg:repoze.zodbconn#closer’ middleware.Add blobstorage and demostorage support to zeo and file resolvers.0.2 (unknown)Unknown changes0.1 (unknown)Initial release.