Commit 668dc2af authored by Jim Fulton's avatar Jim Fulton

Switch to src/CHANGES.txt with a simpler format from NEWS.txt.

parent ba955c39
What's new in ZODB 3.9.0
========================
General
-------
Change History
**************
- (3.9.0a1) Document conflict resolution (see ZODB/ConflictResolution.txt).
3.9.0a1 (2008-??-??)
====================
- (3.9.0a1) Bugfix the situation in which comparing persistent objects (for
instance, as members in BTree set or keys of BTree) might cause data
inconsistency during conflict resolution.
New Features
------------
- Versions are no-longer supported.
- ZEO cache files can be larger than 4G. Note that lder ZEO cache
files are not supported.
- Document conflict resolution (see ZODB/ConflictResolution.txt).
- (3.9.0a1) Support multidatabase references in conflict resolution.
- Support multidatabase references in conflict resolution.
- (3.9.0a1) Make it possible to examine oid and (in some situations) database
- Make it possible to examine oid and (in some situations) database
name of persistent object references during conflict resolution.
- (3.9.0a1) Moved 'transaction' module out of ZODB.
- Moved 'transaction' module out of ZODB.
ZODB depends upon this module, but it must be installed separately.
- (3.9.0a1) ZODB installation now requires setuptools.
- ZODB installation now requires setuptools.
- (3.9.0a1) Added `offset` information to output of `fstail`
- Added `offset` information to output of `fstail`
script. Added test harness for this script.
- (3.9.0a1) Fixed bug 153316: persistent and BTrees were using `int`
for memory sizes which caused errors on x86_64 Intel Xeon machines
(using 64-bit Linux).
- (3.9.0a1) Removed version support from connections and DB. Versions
are still in the storages; this is an incremental step.
- (3.9.0a1) Added support for read-only, historical connections based
- Added support for read-only, historical connections based
on datetimes or serials (TIDs). See
src/ZODB/historical_connections.txt.
Bugs Fixed
----------
- Bugfix the situation in which comparing persistent objects (for
instance, as members in BTree set or keys of BTree) might cause data
inconsistency during conflict resolution.
- Fixed bug 153316: persistent and BTrees were using `int`
for memory sizes which caused errors on x86_64 Intel Xeon machines
(using 64-bit Linux).
- (3.9.0a1) Fixed small bug that the Connection.isReadOnly method didn't
- Fixed small bug that the Connection.isReadOnly method didn't
work after a savepoint.
ZEO
---
- (3.9.0a1) Bug #98275: Made ZEO cache more tolerant when invalidating current
- Bug #98275: Made ZEO cache more tolerant when invalidating current
versions of objects.
- (3.9.0a1) Fixed a serious bug that could cause client I/O to stop
- Fixed a serious bug that could cause client I/O to stop
(hang). This was accomonied by a critical log message along the
lines of: "RuntimeError: dictionary changed size during iteration".
Transactions
------------
- (3.9.0a1) 'transaction' module is not included in ZODB anymore. It
is now just a ZODB dependency (via setuptools declarations).
Blobs
-----
- Fixed bug #127182: Blobs were subclassable which was not desired.
- (3.9.0a1) Fixed bug #127182: Blobs were subclassable which was not desired.
- (3.9.0a1) Fixed bug #126007: tpc_abort had untested code path that was
- Fixed bug #126007: tpc_abort had untested code path that was
broken.
- (3.9.0a1) Fixed bug #129921: getSize() function in BlobStorage could not
- Fixed bug #129921: getSize() function in BlobStorage could not
deal with garbage files
- (3.9.0a1) Fixed bug in which MVCC would not work for blobs.
BTrees
------
-
- Fixed bug in which MVCC would not work for blobs.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment