Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Z
ZEO
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
Kirill Smelkov
ZEO
Commits
f9811946
Commit
f9811946
authored
Mar 20, 2005
by
Chris McDonough
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
No commit message
No commit message
parent
6b8ad30e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
24 additions
and
0 deletions
+24
-0
NEWS.txt
NEWS.txt
+24
-0
No files found.
NEWS.txt
View file @
f9811946
...
...
@@ -40,6 +40,30 @@ BTrees
scores in an ``IIBTree``, and Zope3 has moved to ``IFBTrees``
for these purposes in its search code.
FileStorage
-----------
- Add a record iteration protocol to FileStorage. You can use the
record iterator to iterate over all current revisions of data
pickles in the storage.
In order to support calling via ZEO, we don't implement this as an
1actual iterator. An example of using the record iterator protocol
is as follows:
storage = FileStorage('anexisting.fs')
next_oid = None
while 1:
oid, tid, data, next_oid = storage.record_iternext(next_oid)
# do something with oid, tid and data
if next_oid is None:
break
The behavior of the iteration protocol is now to iterate over all
current records in the database in ascending oid order, although
this is not a promise to do so in the future.
Tools
-----
...
...
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