[Developers] sandbox caching old values, slow expiration?

[Arthur van Hoff]

I'm running into the caching problem in my python app. Within the same
app I do some writes, followed by a read, and I get old data. I'm
writing a http server, so it may be due to the multi threaded nature of
my application. 

 

Can someone remind me how to work around this problem?

 

Somebody suggested doing an empty mqlwrite, but that seems too expensive
if I have to do it before every mqlread, just in case the cache is
stale.

 

From: developers-bounces at freebase.com
[mailto:developers-bounces at freebase.com] On Behalf Of Coral Link
Sent: Saturday, December 29, 2007 5:51 AM
To: developers at freebase.com
Subject: [Developers] sandbox caching old values, slow expiration?

 

Hi, quite a few times while working on my app I've run into instances
when I've made updates/changes to objects in the sandbox BUT when I
query the just changed object, I get its old values.  I  run my queries
in queryeditor, and the values returned are the updated ones. After some
magical period, the mqlwrite/mqlread service starts showing the expected
values. 

Is there some sort of caching going on?  What are the timeouts if any,
to pull the most current values from the repository?  Is there some sort
of tickle mechanism to ask mqlread to pull a fresh copy instead of a
cached on? 

Thank you and kind regards,
Indy



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/developers/attachments/20080130/da66ccbf/attachment.htm