On 3/27/07, Oleg Broytmann <[EMAIL PROTECTED]> wrote: > Hello! > > Why not just > conn.cache.clear()
Yes, you are right, that would of course be the better solution. However, it seems that I can avoid the problem by performing just the SQLObject relevant part of code in the function passed to doInTransaction(), and have the rest of the code outside of that function. It seems that the values only stay in the cache if the GUI relevant code was also in the function which I passed to doInTransaction(). So probably just false alarm :) However I have one more question: I used to set the connection using sqlhub.processConnection = connectionForURI(...) which is the way the SQLObject documentation describes at http://www.sqlobject.org/ and http://www.sqlobject.org/SQLObject.html. To switch between different databases, I set sqlhub.processConnection to the desired DB, which worked fine. Now, after calling doInTransaction() this works no more. I suppose the problem is, that doInTransaction() restores the old connection unconditionally to sqlhub.threadConnection, although self.getConnection() returned the sqlhub.processConnection in my case. And since sqlhub.threadConnection is set now, changing sqlhub.processConnection in my code has no effect anymore. Kind regards, Markus ------------------------------------------------------------------------- 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 sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
