Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
ZODB
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
ZODB
Commits
935cebfc
Commit
935cebfc
authored
Oct 16, 2008
by
Jim Fulton
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Prep for final release.
parent
aec3292e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
20 deletions
+23
-20
NEWS.txt
NEWS.txt
+23
-20
No files found.
NEWS.txt
View file @
935cebfc
...
...
@@ -9,70 +9,73 @@ Bugs Fixed:
during Zope2's auto-refresh of products.
(https://bugs.launchpad.net/zodb/+bug/142667).
- (
beta 9
) An exception would be raised when an error occured attempting to
- (
3.8.1
) An exception would be raised when an error occured attempting to
lock a file and logging of said error was enabled.
- (
beta 9
) Fixed a bug to allow opening of deep-copied blobs.
- (
3.8.1
) Fixed a bug to allow opening of deep-copied blobs.
- (
beta 9
) Fixed bug #189542 by prepending the module to an undefined name.
- (
3.8.1
) Fixed bug #189542 by prepending the module to an undefined name.
- (beta 8) If there is a failure while FileStorage is finalizing a transaction,
- (3.8.1) Failures in tpc_finish of client-storages weren't handled
correctly, leaving the client storage in an inconsistent state.
- (3.8.1) If there is a failure while FileStorage is finalizing a transaction,
the file storage is closed because it's internal meta data may be
invalid.
- (
beta 8
) FileStorages previously saved indexes after a certain
- (
3.8.1
) FileStorages previously saved indexes after a certain
number of writes. This was done during the last phase of two-phase
commit, which made this critical phase more subject to errors than
it should have been. Also, for large databases, saves were done so
infrequently as to be useless. The feature was removed to reduce
the chance for errors during the last phase of two-phase commit.
- (
beta 8
) File storages previously kept an internal object id to
- (
3.8.1
) File storages previously kept an internal object id to
transaction id mapping as an optimization. This mapping caused
excessive memory usage and failures during the last phase of
two-phase commit. This optimization has been removed.
- (
beta 8
) Fixed a bug that caused deep copying of blobs to fail.
- (
3.8.1
) Fixed a bug that caused deep copying of blobs to fail.
- (
beta 8
) Refactored handling of invalidations on ZEO clients to fix
- (
3.8.1
) Refactored handling of invalidations on ZEO clients to fix
a possible ordering problem for invalidation messages.
- (
beta 8
) An ZEO cache internal data structure can get out of sync
- (
3.8.1
) An ZEO cache internal data structure can get out of sync
with the data in a way that prevents data from being loaded into the
cache. We don't yet know why, but added an exception handler to
prevent this error from being fatal.
- (
beta 8
) Fixed setup.py use of setuptools vs distutils, so .c and .h
- (
3.8.1
) Fixed setup.py use of setuptools vs distutils, so .c and .h
files are included in the bdist_egg.
- (
beta 8
) On many systems, it was impossible to create more than 32K
- (
3.8.1
) On many systems, it was impossible to create more than 32K
blobs. Added a new blob-directory layout to work around this
limitation.
- (
beta 7
) Fixed a bug, introduced in an earlier beta, that allowed
- (
3.8.1
) Fixed a bug, introduced in an earlier beta, that allowed
clients to connect to out of date servers.
- (
beta 7
) Fixed bug that could lead to memory errors due to the use
- (
3.8.1
) Fixed bug that could lead to memory errors due to the use
of a Python dictionary for a mapping that can grow large.
- (
beta 7
) Fixed bug #251037: Made packing of blob storages non-blocking.
- (
3.8.1
) Fixed bug #251037: Made packing of blob storages non-blocking.
- (
beta 6
) Fixed a bug that could cause InvalidObjectReference errors
- (
3.8.1
) Fixed a bug that could cause InvalidObjectReference errors
for objects that were explicitly added to a database if the object
was modified after a savepoint that added the object.
- (
beta 5
) Fixed several bugs that caused ZEO cache corruption when connecting
- (
3.8.1
) Fixed several bugs that caused ZEO cache corruption when connecting
to servers. These bugs affected both persistent and non-persistent caches.
- (
beta 5
) Improved the the ZEO client shutdown support to try to
- (
3.8.1
) Improved the the ZEO client shutdown support to try to
avoid spurious errors on exit, especially for scripts, such as zeopack.
- (
beta 4
) Packing failed for databases containing cross-database references.
- (
3.8.1
) Packing failed for databases containing cross-database references.
- (
beta 3
) Cross-database references to databases with empty names
- (
3.8.1
) Cross-database references to databases with empty names
weren't constructed properly.
- (
beta 2
) The cache used an excessive amount of memory, causing applications
- (
3.8.1
) The cache used an excessive amount of memory, causing applications
with large caches to exhaust available memory.
- Fixed a number of bugs in the handling of persistent ZEO caches:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment