I have the same problem... my webpage is suddenly frustrating for many users because of this newly introduced latency... I don't know what to say but this is not what I expected from google... When something is submitted you're being redirected to it - but it results in 404 because the datastore seems to not work properly any more... It's been like this for more than a day now...
:( On Sep 19, 7:08 am, Andreas Krohn <[EMAIL PROTECTED]> wrote: > Changes made to datastore entities are not available via GQL requests. > My users can change some configurations, these configs are stored in > the datastore and then retreived there via a GQL request and get(). > The problem is that the GQL request picks up the old values (ie before > the user changed the config) and not the new ones. I am not using > Memcache or any other cache as far as I am aware of. > > If I take a look in the users admin panel the value shown there is > correct, and this is also picked up via a GQL get() request. What I > suspect is happening is that the Datastore caches the requests somehow > and I just get the cached value, not the current value. > > Is there such a datastore cache in place? If there is, how do I get > around it so that I am sure that I am always getting the current > value? > > Thanks > /Andreas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
