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
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Nicolas Wavrant
ZODB
Commits
be4f7918
Commit
be4f7918
authored
Oct 29, 2008
by
Jim Fulton
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Documented new DemoStorage and MappingStorage features.
Moved size-limiting-cache feature to future release, since it
parent
d03edc44
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
30 additions
and
12 deletions
+30
-12
src/CHANGES.txt
src/CHANGES.txt
+30
-12
No files found.
src/CHANGES.txt
View file @
be4f7918
...
@@ -2,12 +2,41 @@
...
@@ -2,12 +2,41 @@
Change History
Change History
================
================
3.9.0a1 (2008-??-??)
3.9.0a2 (2008-??-??)
====================
- The connection now estimates the object size based on its pickle size
and informs the cache about size changes.
The database got additional configurations options (`cache-size-bytes`
and `historical-cache-size-bytes`) to limit the
cache size based on the estimated total size of cached objects.
The default values are 0 which has the interpretation "do not limit
based on the total estimated size".
There are corresponding methods to read and set the new configuration
parameters.
XXX There are known issues with this implementation that need to be
sorted out before it is "released".
3.9.0a1 (2008-10-29)
====================
====================
New Features
New Features
------------
------------
- MappingStorage now supports multi-version concurrency control and
iteration and provides a better storage implementation example.
- DemoStorage has a number of new features:
- The ability to use a separate storage, such as a file storage to
store changes
- Blob support
- Multi-version concurrency control and iteration
- Wen calling ZODB.DB to create a database, you can now pass a file
- Wen calling ZODB.DB to create a database, you can now pass a file
name, rather than a storage to use a file storage.
name, rather than a storage to use a file storage.
...
@@ -34,17 +63,6 @@ New Features
...
@@ -34,17 +63,6 @@ New Features
option can avoid effective downtimes in the order of hours when
option can avoid effective downtimes in the order of hours when
the connection to the ZEO server was interrupted for a longer time.
the connection to the ZEO server was interrupted for a longer time.
- The connection now estimates the object size based on its pickle size
and informs the cache about size changes.
The database got additional configurations options (`cache-size-bytes`
and `historical-cache-size-bytes`) to limit the
cache size based on the estimated total size of cached objects.
The default values are 0 which has the interpretation "do not limit
based on the total estimated size".
There are corresponding methods to read and set the new configuration
parameters.
- Cleaned-up the storage iteration API and provided an iterator implementation
- Cleaned-up the storage iteration API and provided an iterator implementation
for ZEO.
for ZEO.
...
...
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