Tonny, Tonny Staunsbrink wrote: > Since cherrypy is multi threaded, could it be that each thread has it > own version of the user object? If that is on purpose, what am I doing > wrong. How should I update the user object?
I'm not sure if I understood your problem entirely but SQLObject provides an expire() method which you can use to force SQLObject to get new values from the database. e.g. user.expire() I think it would help if you can provide a small self-contained test case. Of course, writing test cases is not easy but they help us diagnosing the problem. Speaking from my own experience, I find the error in approx. 80% before even sending the test case to the list. Furthermore a separate test case speeds up debugging. hth -- Felix Schwarz software development and Linux system administration main focus: secure database applications Gubener Str. 38 10243 Berlin Germany --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
