[John Ehresman]
> This will be fixed in the WingDBG product. There's no need to resurrect
> the sub() method because it's easy to change the product to not require a
> subtransaction.
Since, despite its name, the sub() method had nothing to do with
subtransactions anyway (see earlier msg), that's
> From: Tim Peters <[EMAIL PROTECTED]>
>> WingDBG does this: tx = get_transaction().sub()
>
> Nope, it's not. It's a consequence of just moving beyond ZODB 3.2.
> Transactions in ZODB 3.3 and 3.4 have never had a .sub() method
> (that's been true for over a year). A transaction object in ZODB 3.
[Lennart Regebro]
> WingDBG does this: tx = get_transaction().sub()
> That fails because 'Transaction' object has not attribute 'sub'. This
> is obviously an effect of the moving from subtransactions to
> checkpoints.
Nope, it's not. It's a consequence of just moving beyond ZODB 3.2.
Transaction
WingDBG does this: tx = get_transaction().sub()
That fails because 'Transaction' object has not attribute 'sub'.
This is obviously an effect of the moving from subtransactions to checkpoints.
transaction.get() has the same effect, btw.
Question: Is it Zope2.8 that is wrong or WingDBG?
--
Lennart
