Sorry my bad - I think I just found out what did it in my code. Cheers
Chris On Nov 1, 3:06 pm, Aaron Boodman <[EMAIL PROTECTED]> wrote: > There's no caching behavior in the database API that I know of. Can > you give a small sample that shows this behavior? > > - a > > On Fri, Oct 31, 2008 at 9:42 PM, Khookie <[EMAIL PROTECTED]> wrote: > > > This behaviour occurs randomly, thus I haven't been able to produce > > source code... but sometimes when I update data in a GearsDatabase, > > and then fetch the row again soon after (e.g. perhaps 1-2 seconds > > later via a different query), the old data comes back... but give it a > > few more seconds, and the new (and correct) data comes back. > > > So I'm just wondering, does GearsDatabase have some sort of caching > > mechanism built in? Has anyone experienced this sort of behaviour? > > Is there something I can do to avoid this? > > > Chris
