Commit 1b6f7156 authored by Jim Fulton's avatar Jim Fulton

Update IStorage.load to reflect it's diminished status

parent 227953b9
......@@ -577,6 +577,20 @@ class IStorage(Interface):
def load(oid, version):
"""Load data for an object id
NOTE: This method is deprecated and may be removed in the
future. It is no longer used by ZODB, although it may still
be used in some tests or scripts. Previously, there was a
requirement that load results be properly ordered with
invalidations so that at any point in time, clients have a
consistent view of what version of an object is current. This
restriction has been relaxed and some storages will be
simplified as a result of the removal of this requirement.
An alternative to calling load is calling loadBefore passing
ZODB,utils.maxtid::
store.loadBefore(oid, ZODB.utils.maxtid)
The version argumement should always be an empty string. It
exists soley for backward compatibility with older storage
implementations.
......
......@@ -34,6 +34,7 @@ __all__ = ['z64',
'u64',
'U64',
'cp',
'maxtid',
'newTid',
'oid_repr',
'serial_repr',
......@@ -102,6 +103,8 @@ else:
z64 = b'\0' * 8
maxtid = b'\xff' * 8
assert sys.hexversion >= 0x02030000
# The distinction between ints and longs is blurred in Python 2.2,
......
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