> > If you just need to store data for a single user across requests, you can > store it in the session (each user has a separate session). But if you need > to store data from multiple users and then process it all together, you can > store it in the cache: http://web2py.com/books/default/chapter/29/4#cache. > > > That might be just slightly unsafe, don't you think, if a piece of data > gets evicted before it's needed? I'd prefer to limit caching to data that > can be recreated when it's not found in the cache. > > An alternative might be a memory-based SQLite database, taking care not to > let it leak (a consideration regardless of the implementation). >
Doesn't a memory-based db have the same problem -- you have to purge at some point and could therefore "evict" data before it's needed in that case as well? Also, is there a way to persist a memory-based SQLite db in web2py? I thought they would only persist for a single request. Anthony
