-
Notifications
You must be signed in to change notification settings - Fork 2
/
Copy pathCHANGES.txt
199 lines (140 loc) · 6 KB
/
CHANGES.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
``repoze.zodbconn`` Changelog
=============================
0.15 (2013-07-22)
-----------------
- Worked around broken stdlib ``urlsplit`` implementations which jam
the ``fragment`` for 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 the ``repoze.zodbconn.connector`` middleware 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's ``im_self`` as the connection, rather than opening a new
connection.
- Extend ``repoze.zodbconn.connector`` middleware 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's ``urlparse``
module 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 a ``zconfig`` URI parser, providing basic support for any
kind of storage that ZODB can load via ZConfig.
- Added a ``db_from_uri`` function, which is simpler to use than
``dbfactory_from_uri``; ``db_from_uri`` also supports
multi-databases. Replaced references in the documentation.
- Added ``connector``, a WSGI framework component that connects to ZODB
and puts the connection in the WSGI environment. It unconditionally
closes the ZODB connection on exit.
- ``PersistentApplicationFinder`` now gets the ZODB connection
from the WSGI environment whenever it is provided.
- Moved ``db_from_uri`` and ``dbfactory_from_uri`` to a module
named ``uri``, to avoid circular imports.
- Added ``cachecleanup``, a WSGI framework component that keeps only
objects of certain classes in the ZODB cache. This helps control
memory consumption.
- Added ``transferlog``, a WSGI framework component that logs
how many ZODB objects were loaded and stored per request.
0.9.1 (2009-06-12)
------------------
- The ``EnvironmentDeleterMiddleware`` (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)
----------------
Features
--------
- Added a ``LoggingCleanup`` implementation which can be passed to
``PersistentApplicationFinder``: 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.
- Added ``cleanup`` argument to constructor of ``PersistentApplicationFinder``,
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 Fixes
---------
- Fixed breakage with ``file:`` URIs having no query string.
0.8 (2009-05-25)
----------------
Features
--------
Fix 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)
----------------
Features
--------
Added 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 Incompatibilities
----------------------------
``dbfactory_from_uri`` now returns only a single argument (the
factory).
Features
--------
Docs updated with argument values for ``file://`` and ``zeo://`` URI
schemes; this file converted to real REST.
0.5 (unknown)
-------------
Pass ``layout`` to BlobStorage as a kwarg explicitly (for forward
compatibility).
Depend on ZODB3 3.8.1+.
0.4 (unknown)
-------------
Add ``connection_cache_size``, ``connection_pool_size``, and
``database_name`` arguments to both FileStorage and ClientStorage URI
resolver schemes. ``connection_cache_size`` represents the ZODB
object cache size (the ``cache_size`` parameter to the DB
constructor), ``connection_pool_size`` represents the ZODB connection
pool size (the ``pool_size`` parameter to the DB constructor), and
``database_name`` represents the ZODB database name (the
``database_name`` parameter to the DB constructor).
``connection_cache_size`` defaults to 10000 (overriding the too-low DB
constructor default of 400), ``connection_pool_size`` defaults to 7,
and ``database_name`` defaults to ``unnamed``.
0.3 (unknown)
-------------
Add 'egg:repoze.zodbconn#closer' middleware.
Add blobstorage and demostorage support to zeo and file resolvers.
0.2 (unknown)
-------------
Unknown changes
0.1 (unknown)
-------------
Initial release.