Quoting John Speno <[EMAIL PROTECTED]>:
As all of our sqlobjects have 'cacheValues = False' set. Obviously, this didn't help the transaction problem before the fix, bu should the fix introduced in r1581 to cache.py fix our inconsistency problems?
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. Kevin's message below (referenced in the tracker patch that 1581 implemented) describes the consistency problem: http://pythonpaste.org/archives/message/20051129.172427.0ec7941f.en.html Couldn't quite understand your situation, is using cacheValues=False NOT solving the cache inconsistency? If that's the case, the inconsistency you're talking about is not one I'm familiar with, I echo Oleg's request for a test script showing the problems. - Luke ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ sqlobject-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
