Andreas Jung wrote at 2007-5-1 11:23 +0200:
...
I think you are right (as always). Then let me rephrase the question: how
can one distinguish if two transaction objects represent the same or
different transactions in such case where memory address is identical?
Why are you interested in such a
--On 4. Mai 2007 19:58:47 +0200 Dieter Maurer [EMAIL PROTECTED] wrote:
Andreas Jung wrote at 2007-5-1 11:23 +0200:
...
I think you are right (as always). Then let me rephrase the question:
how can one distinguish if two transaction objects represent the same or
different transactions in
Andreas Jung wrote at 2007-5-4 21:13 +0200:
--On 4. Mai 2007 21:05:00 +0200 Dieter Maurer [EMAIL PROTECTED] wrote:
But, the transactions are not concurrent in your original description!
Instead, one transaction has been committed and (only!) then you
see a transaction with the same id again.
[Andreas Jung]
I encountered the following strange behavior with Zope 2.8.8.
I couldn't find a problem in the following. Are you having a
problem, or just asking a question?
The following code is used to integrate SQLAlchemy with
Zope. A registered utility subclassing ZopeBaseWrapper
