[Developers] mqlread queries and caching

[Christian Hirsch]

Hi,

I have the same problem as Augusto:

> at time t1 i run a query and get back results.
> at time t2 i perform mqlwrite operations.
> at time t3 i rerun the query i ran at time t1, expecting to see the
changes i made at t2, but only see the results at t1.

A Java Applet is performing the read queries. The write is done from
freebase.com.

In order to solve the caching problem I've added a call to
/api/service/touch between t2 and t3. This is also done by the applet (and I
do get the status 200 ok response... so this should work...)

However, I still get the old query results at t3. What could the problem be?


Thanks,
Christian


On Sat, Sep 6, 2008 at 11:31 AM, Augusto Callejas <
acallejas at appliedminds.com> wrote:

> hi-
>
> my question is about the caching that occurs when you query
> /api/service/mqlread.
>
> at time t1 i run a query and get back results.
> at time t2 i perform mqlwrite operations.
> at time t3 i rerun the query i ran at time t1, expecting to see the changes
> i made at t2, but only see the results at t1.
>
> (times are t1 < t2 < t3)
>
> i understand the use of query caching for performance reasons, but i need a
> way to get the changes i made at t2 at some future point using the query i
> made at t1.
>
> can i:
>
> 1) disable query caching from the client side on a per-query basis?
> 2) determine programmatically what time the results of a query (in this
> case, the results of querying at time t3 would indicate that the results
> were valid at t1) were valid at?
> 3) know how long a cache of query results stays alive for?
>
> thanks,
> augusto.
>
>
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/developers/attachments/20080910/2d87f3fc/attachment.htm