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

2010-09-23 Thread Jim Fulton
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

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

2010-09-23 Thread Stephan Richter
On Thursday, September 23, 2010, Jim Fulton wrote: Comments? Sounds good and addresses my concerns raised in the discussion of the bug. Regards, Stephan -- Entrepreneur and Software Geek Google me. Zope Stephan Richter ___ For more information about

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

2010-09-23 Thread Hanno Schlichting
On Thu, Sep 23, 2010 at 4:24 PM, Jim Fulton j...@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

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

2010-09-23 Thread Marius Gedminas
On Thu, Sep 23, 2010 at 10:53:03AM -0400, Stephan Richter wrote: On Thursday, September 23, 2010, Jim Fulton wrote: Comments? Sounds good and addresses my concerns raised in the discussion of the bug. What bug? Marius Gedminas -- Being really good at C++ is like being really good at using