In the document of cherrypy[1]:
If you want to use transactions you should also turn _cacheValues
off, like:
class Person(SQLObject):
_cacheValue = False
This, though, makes attribute access very slow (SQLObject queries
database for an every attribute access).
If one wants to set _cacheValue = True one has to synchronize
objects between threads herself.
But, the problem seems to be fixed in rev.1581 [2]:
The fix in r1581 was originally written in order to allow using
cacheValues=True with Transactions. So if you're using False to
avoid the
consistency problems, r1581 should allow you to go back to
cacheValues=True.
I've wrote a small script that rollback a transaction with SQLObjects
using cacheValues = True and tried it, then it works rightly.
it's ok that "the problem is fixed now" and "the document has not
been updated yet" ?
[1] http://www.sqlobject.org/SQLObject.html#transactions
[2] http://www.w4py.org/archives/mindex/sqlobject-
[EMAIL PROTECTED]/message/
20060208.174055.fb3bbc3d.en.html
-- masayuki.takagi
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
