Usage of z64/None as "no transaction" marker is inconsistent

Bug #192894 reported by Christian Theune
2
Affects Status Importance Assigned to Milestone
ZODB
Fix Released
Undecided
Unassigned

Bug Description

While working on Bug #181712 we discovered that the use of z64 or None as the marker for "no previous transaction" is inconsistent.

In the original bug we decided that we should make it consistent. I'm opening another bug specially for this because this is out of scope for the originally reported bug.

Revision history for this message
Jim Fulton (jim-zope) wrote :

Is this still an issue? If so, could you please be more specific? Where and in what way are signaling of "no previous transaction" inconsistent?

Jim Fulton (jim-zope)
Changed in zodb:
status: New → Incomplete
Revision history for this message
Christian Theune (ctheune) wrote :

In the case of empty storages:

MappingStorage: lastTransaction returns ltid which is initialized with None
FileStorage: lastTransaction returns ltid with is initialized with the index which uses z64 on empty storages
DemoStorage: lastTransaction returns what its base returns
ClientStorage: returns None

So by looking at it, it's basically FileStorage which returns z64, the others tend to use None.

Some details of this were already discussed around here https://bugs.edge.launchpad.net/zodb/+bug/181712/comments/7 but haven't been checked in because the patch never got feedback.

Changed in zodb:
status: Incomplete → New
Jim Fulton (jim-zope)
Changed in zodb:
milestone: none → 3.10.0b2
milestone: 3.10.0b2 → none
status: New → Fix Committed
Revision history for this message
Jim Fulton (jim-zope) wrote :

will be in 3.10 b7

Changed in zodb:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.