On GAE, in this statement
results = db(auth.settings.table_user.name=="Joe").select(cache=
(self.cache.ram,3600))
the cache is not used. The cache statement is ignored so no need to
clear the cache.
Probably this will be fixed in the new DAL.
You can cache the records yourself
results=cache.memcache('myrecords': lambda: db
(auth.settings.table_user.name=="Joe").select(cache=(self.cache.ram,
3600)).as_list(),5000)
and clear it with
cache.memcache.delete('myrecords') ### memcache only syntax
Anyway, I am skeptical you get any speed up out of all this.
Massimo
On Jul 16, 6:28 pm, Dan <[email protected]> wrote:
> so would I need to run a new query? is that the only way to remove the
> old/invalid results when running on GAE?
>
> On Jul 16, 4:03 pm, mdipierro <[email protected]> wrote:
>
> > correction. This is DOES NOT supported on GAE.
>
> > On Jul 16, 3:54 pm, mdipierro <[email protected]> wrote:
>
> > > yes
>
> > > cache.ram.clear(regex="....")
>
> > > On 16 Lug, 13:16, Dan <[email protected]> wrote:
>
> > > > Hello- I saw this thread which discusses ways to clear a cached select
> > > > () result on non-GAE platforms. Is there a way to use the cache.clear
> > > > (regex=??) command to remove the results of a known datastore query
> > > > that works on GAE too?
> > > > Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
