All, Okay. This appears related to http://trac.turbogears.org/ticket/1419.
My current fix (big yuck!) is to explictly call session.clear() at each entry point which clears out the cache. This doesn't feel like the right solution but does seem to work in all my test cases... Thanks, Brandon -- On Nov 12, 2007 2:10 PM, Brandon Goldfedder <[EMAIL PROTECTED]> wrote: > This is occurring under both sqlite and MYSQL so not sure what the exact > situation is but basically when invoking queries to TG (using an unused > parameter with a random number to disable app caching) we are sometimes > getting the latest and sometimes an earlier version...Could this be related > to a session flush issue? > > Thanks, > --Brandon > > > On Nov 12, 2007 1:55 PM, Brandon Goldfedder <[EMAIL PROTECTED]> > wrote: > > > All, > > > > I've been seeing a similar issue under SQLAlchemy (using Elixir setup > > with latest update !) under the latest update (and fixing a problem which is > > causing visitors and identity to fails) > > > > --B > > > > > > On Sep 17, 2007 10:11 AM, krsyoung <[EMAIL PROTECTED]> wrote: > > > > > > > > On Sep 16, 6:58 am, "Diez B. Roggisch" <[EMAIL PROTECTED]> > > > wrote: > > > > krsyoung schrieb: > > > > > > > > > On Sep 15, 10:54 am, "Diez B. Roggisch" < > > > [EMAIL PROTECTED]> > > > > > wrote: > > > > >> krsyoung schrieb: > > > > > > > > >>> Hey, > > > > >>> I'm having a caching problem with my application (or so I > > > think). The > > > > >>> problem shows up in both IE and Firefox (settings to Load Page > > > Every > > > > >>> Visit). In the controller I have code like: > > > > >>> [..snip..] > > > > >>> Is it possible that a) SQLObject has multiple versions of the > > > object > > > > >>> hanging around and is passing an old version to the "view" > > > template? > > > > >>> b) Somehow this is a browser issue and it just can't seem to > > > guess > > > > >>> when a page has been updated and when it hasn't? > > > > >>> Any ideas what I could try to confirm a or b or maybe a better > > > way to > > > > >>> write the code to avoid the issue? > > > > >> Are you doing this using AJAX? Then try appending a > > > tg_random-named > > > > >> parameter containing e.g. the current timestamp to the request. > > > That > > > > >> should solve caching issues. > > > > > > > > >> I don't presume there is a SO-problem. > > > > > > > > >> diez > > > > > > > > > Hey Diez, > > > > > > > > > Thanks for the suggestion. I'm not using AJAX for this particular > > > > > > > > portion. Here is something else I just saw that confuses me even > > > > > more. On the "view" screen I also have a list of events printed > > > out. > > > > > One event that I record is a request put on hold, or resumed. > > > This > > > > > list is always correct (I basically pass select * from events to > > > the > > > > > view template). > > > > > > > > > So, it is only the request portion of template that is caching. I > > > > > also added a print request directly in the template and sure > > > enough it > > > > > doesn't show the new state values. However, if I navigate away > > > from > > > > > the page them come back to it I get the same results (sometimes on > > > > > hold, sometimes in progress). > > > > > > > > > I really wanted to blame IE for the problem, but looks like that > > > one > > > > > won't work this time :-) > > > > > > > > Strange. I've never experienced such a behavior with SO - but there > > > are > > > > caches in there you might consider turning off. But I'm not sure how > > > to > > > > do so right here and now. > > > > > > > > Diez > > > > > > Hey, > > > > > > I found another post which seems to be suffering a similar issue: > > > > > > http://groups.google.com/group/turbogears/browse_thread/thread/318d32bda9ebf47f/9cdf0540a1b91040 > > > > > > Sure enough, if I switch to MySQL (which caused another problem!) the > > > caching issue goes away. Solution for me right now is going to be to > > > move dev environment to MySQL :-) > > > > > > Thanks for the ideas > > > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
