11
- A ZEO threading bug could cause transactions to read inconsistent
12
data. (This sometimes caused an AssertionError in
13
Connection._setstate_noncurrent.)
15
- DemoStorage.loadBefore sometimes returned invalid data which
16
would trigger AssertionErrors in ZODB.Connection.
18
- History support was broken when using stprages that work with ZODB
21
- zope.testing was an unnecessary non-testing dependency.
23
- Internal ZEO errors were logged at the INFO level, rather
24
than at the error level.
26
- The FileStorage backup and restore script, repozo, gave a
27
deprecation warning under Python 2.6.
29
- C Header files weren't installed correctly.
37
- 2 BTree bugs, introduced by a bug fix in 3.9.0c2, sometimes caused
38
deletion of keys to be improperly handled, resulting in data being
39
available via iteraation but not item access.
47
- ZEO manages a separate thread for client network IO. It created
48
this thread on import, which caused problems for applications that
49
implemented daemon behavior by forking. Now, the client thread
50
isn't created until needed.
52
- File-storage pack clean-up tasks that can take a long time
53
unnecessarily blocked other activity.
55
- In certain rare situations, ZEO client connections would hand during
56
the initial connection setup.
11
- Conflict errors committing blobs caused servers to stop committing
64
- Conflict errors committing blobs caused ZEO servers to stop committing
added
removed
src/CHANGES.txt
