Casey Duncan wrote:

I would argue that a better plan would be to only use _v_ vars for completely disposable data only. The application should expect that this values will be gone at any random time, not just at transaction boundaries.

I agree with this. How do we go about find code that uses the assumption that _v_ stuff won't change unless it's at a transaction boundary?


Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - )

Reply via email to