Actually I was wrong. If you update a record it does not update the cached ones.
On Monday, September 10, 2012 11:29:02 AM UTC-5, Felipe Meirelles wrote: > > Oh, thats nice, all just works the way I use to work with GAE cache. > > Great work Massimo, hope I can start to contribute soon. > > Thank you. > > On Mon, Sep 10, 2012 at 1:08 PM, Massimo Di Pierro > <massimo....@gmail.com<javascript:> > > wrote: > >> You cannot invalidate a single row if you are caching the all set of rows. >> >> Mind that if you do rows.update_records(...) and rows is cached, it >> should update the cached row as well. >> >> >> On Monday, 10 September 2012 08:16:07 UTC-5, Felipe Meirelles wrote: >> >>> But it will invalidate all the cache data. I want to invalidate just one >>> row cache, is this possible? >>> >>> On Mon, Sep 10, 2012 at 10:14 AM, Massimo Di Pierro < >>> massimo....@gmail.com> wrote: >>> >>>> If you use cache.ram or cache.disk you can do >>>> >>>> cache.ram.clear() >>>> cache.disk.clear() >>>> >>>> this will clear all ram. You can also pass a regex to clear to clear >>>> only some keys. >>>> >>>> On Monday, 10 September 2012 07:49:27 UTC-5, Felipe Meirelles wrote: >>>>> >>>>> Only one more question, can I enforce the cache to invalidate (as when >>>>> I know the record has changed) or update the select cache manulay? >>>>> >>>>> On Monday, September 10, 2012 9:44:18 AM UTC-3, Massimo Di Pierro >>>>> wrote: >>>>>> >>>>>> 2.0.8 is known to work fine on GAE. >>>>>> >>>>>> On Monday, 10 September 2012 07:05:11 UTC-5, Felipe Meirelles wrote: >>>>>>> >>>>>>> Anyone tested the new 2.0.2 changes on GAE? Should this work fine? >>>>>>> >>>>>>> Can someone tell me how the internals work for this two features and >>>>>>> how to use it? >>>>>>> >>>>>>> Thanks. >>>>>>> >>>>>> -- >>>> >>>> >>>> >>>> >>> >>> >>> >>> -- >>> Att, >>> Felipe Meirelles. >>> >>> -- >> >> >> >> > > > > -- > Att, > Felipe Meirelles. > > --
