[ZODB-Dev] RFC: deprecate transaction user and description fields in favor of extened info and simplify extended info API

Hanno Schlichting hanno at hannosch.eu
Thu Sep 23 11:15:10 EDT 2010


On Thu, Sep 23, 2010 at 4:24 PM, Jim Fulton <jim at zope.com> wrote:
> The user and description fields are somewhat archaic. They can only be
> strings (not unicode) and can as easily be handled as extended info.
>
> I propose to deprecate the 'user' and 'description' attributes, and
> the 'setUser' and 'note' methods and to add a new 'info' attribute
> whose attributes can be set to set extended info.  For example:
>
>   transaction.info.user = u'j1m'

Is this supposed to be extensible in the sense of allowing arbitrary
information?

In that case I'd prefer this to have a dictionary spelling of:

transaction.info[u'user'] = u'j1m'

That would make it easier to look up all available keys and values in
the info attribute.

Hanno


More information about the ZODB-Dev mailing list