Too bad we can specify to cache.disk where we want it to store... -Thadeus
On Thu, Mar 11, 2010 at 9:14 AM, mdipierro <[email protected]> wrote: > On a second read. Most of it is useful but probably the last line is > not what users want. > The effect would not be to cache db(...).select(cache=....), instead > the effect would be to store the entire database in RAM. > > If the server goes down the data is lost. > > Web2py already provides this functionality. You can simply do > > db=DAL('sqlite:memory:') > > Yet is id different from caching. > > I think what you want instead if mount the rambased disk as the cache > folder and then do > > db(...).select(cache=(ram.disk,3600)....) > > so the ram.disk is actually in ram but buffered on disk. > > Massimo > > On Mar 11, 2:58 am, Kuba Kucharski <[email protected]> wrote: >> you could probably use cache.disk with tmpfs(ram-disk) and this will >> result in caching in ram up to limited size >> using tmpfs is described here:http://www.web2py.com/AlterEgo/default/show/223 >> >> -- >> Kuba > > -- > You received this message because you are subscribed to the Google Groups > "web2py-users" 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. > > -- You received this message because you are subscribed to the Google Groups "web2py-users" 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.
