Hello
I'm using transactions in sqlobjects since years in my web application.
But since some months, I receive these exceptions:
in update
hubNoCache.doInTransaction(updateSubscr,self.id)
File
"/usr/lib/python2.5/site-packages/SQLObject-0.10.2-py2.5.egg/sqlobject/dbconnection.py",
line 856, in doInTransaction
conn = old_conn.transaction()
File
"/usr/lib/python2.5/site-packages/SQLObject-0.10.2-py2.5.egg/sqlobject/dbconnection.py",
line 754, in __getattr__
self.assertActive()
File
"/usr/lib/python2.5/site-packages/SQLObject-0.10.2-py2.5.egg/sqlobject/dbconnection.py",
line 678, in assertActive
assert not self._obsolete, "This transaction has already gone
through ROLLBACK; begin another transaction"
AssertionError: This transaction has already gone through ROLLBACK;
begin another transaction
It looks like its related with the mysql server being overloaded. But
I still don't understand why.
I've been looking at the source and don't understand how this can
happen. I never call rollback in my source, and always make
transactions through doInTransaction.
In the traceback I don't understand why there are missing step between
conn = old_conn.transaction() and self.assertActive(). It should go
through the Transaction constructor.
Please help.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
