That restriction was based on the lack of synchronization of instance caches, applied in r1581 & a further fix in r1683. As I recall, those are both after 0.7.
However, if you are *exclusively* using transactions (don't have a main plain connection whose instance cache matters), you can still use cacheValues=True, or you can manually call .sync() on objects outside of the transaction that you want to re-query the database for changes due to a transaction. - Luke P.S. Oleg, SF Patch 1524615 is the last outstanding issue with synchronization that I'm aware of, the problem it solves was introduced with the close argument to Transaction.commit(). With that applied, the docs for the next release should remove the warning about cacheValues & Transactions. Quoting Oleg Broytmann <[EMAIL PROTECTED]>: > On Tue, Aug 01, 2006 at 06:17:31PM +0200, Didrik Pinte wrote: >> From what i've heard/read, because I need transaction support on those >> tables, I can't use an sqlmeta.cacheValues=True. >> >> Question for the list : is it (still) true ? > > I think it's an outdated requirement. I use transactions with > cacheValues=True. > > Oleg. > -- ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sqlobject-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
