[Developers] Caching problem?

[Alec Flett]

It's not really a bug - its more of a feature :)

Its part of our caching strategy - the idea is that if a client hasn't 
done a write, then it doesn't need to see the most updated result of a 
query. so I'm guessing you're writing to www.freebase.com via a browser, 
but you have another script that is doing the read?

There is actually a 2nd cookie called "mwLastWriteTime" that stores a 
token that tells us how current your data is. If present, it tells us 
how current your results should be.. if NOT present, it means "I don't 
care how current my data is" and may give you even older data.

If you really, really, need to refresh this cookie to get new data, you 
should do an empty HTTP POST to /api/service/mqlwrite. I encourage you 
to do this sparingly - this is not a generally supported mechanism yet, 
but it should continue to work for the near future.

Alec

Kirrily Robert wrote:
> I'm working on populating /time/historic_period and related types.  To
> do this, I'm mostly dinking around manually on freebase.com, but I've
> also written myself a little CGI script to help me know where to focus
> my efforts.  Now I'm finding that when I hit "reload" on my script, it
> doesn't pick up changes I've made on freebase.com since I last
> refreshed.  Will Moffat, on IRC, suggested this was a caching bug he'd
> experienced before, and that you could get round it by making a small
> change to the MQL, eg. changing limit 100 to limit 101.  This does
> indeed seem to work, but obviously it's not a real solution.
>
> Is this something that people know about and are looking into?
>
> K.
>
>