[ZODB-Dev] FW: Transaction status codes in the ZODB?

[Chris McDonough]

Jean, I have forwarded this message to the ZODB-Dev list, as that's probably
the place you'll get the most "bang for your buck".

----- Original Message -----
From: "Jean Jordaan" <jean@upfrontsystems.co.za>
To: "Zope@Zope. Org" <zope@zope.org>
Sent: Thursday, May 02, 2002 8:47 AM
Subject: [Zope] Transaction status codes in the ZODB?


> Hi all.
>
> When I run 'fsrecover.py' from
> Zope 2.5.1b1 (source release, python 2.1, linux2)
> on my Data.fs, I get 710888 errors like::
>
>  __main__.ErrorFound: invalid status, ^@, at 23141234
>
> This is output by the following in 'fsrecover.py'::
>
>     if status not in ' up':
>         error('invalid status, %s, at %s', status, pos)
>
> Where are the status codes documented? How do they get set to invalid
> values? From FileStorage.py I can make some guesses:
>
> 'u' == undone
> 'c' == checkpoint
> ' ' == dunno?
> status=packing and 'p' or ' '
>
> But how/where does status get assigned values such as ^@ (ascii value
> zero)? The returned codes are:
>
> ^@, ^F, , ^M, ^R, ^_, %, +, 7, <, @, D, T, ^, k, {, ~, ^?, <8E>, <92>,
> <95>, <96>, <98>, <9A>, <A9>, <AA>, <AD>, <B4>, <B7>, <C6>, <CA>, <CD>,
> <DF>, <E3>, <E7>, <E9>, <EA>, <FA>
>
> for what that's worth ..
>
> --
> Jean Jordaan
> Upfront Systems                         http://www.upfrontsystems.co.za
>
>
>
> _______________________________________________
> Zope maillist  -  Zope@zope.org
> http://lists.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  http://lists.zope.org/mailman/listinfo/zope-announce
>  http://lists.zope.org/mailman/listinfo/zope-dev )
>