I like the proposal very much. Will be very useful. In the project I am working with, we need to create a lot of temporary tables. And memory seemed very good option.
On Apr 13, 8:22 pm, Iceberg <[email protected]> wrote: > If you are talking about where to store those *.table files, how about > just store them inside a "system_table" in the db=SQLDB > ('sqlite:....')? In this way perhaps we don't need *.table > anymore.... but I might be wrong. :P > > On Apr14, 0:02am, mdipierro <[email protected]> wrote: > > > Here is a proposal > > > db=SQLDB('sqlite:memory:appname',cache=cache.ram) > > > Working on this but the problem is determining whether tables are > > there or need to be created. > > > Massimo > > > On Apr 13, 10:30 am, Iceberg <[email protected]> wrote: > > > > This is a topic with long > > > history.http://groups.google.com/group/web2py/msg/df79e41f2298bef2 > > > > Hopefully Massimo will eventually find a way to implement a ram based > > > db. :-) > > > > On Apr13, 10:44pm, vihang <[email protected]> wrote: > > > > > There maybe something wrong in my understanding, in which case please > > > > correct me, but db objects created using sqlite:memory: are not > > > > persistant. i.e. insert does not work? Is this is a bug ? If not, > > > > could someone tell me what it is suppose to do? > > > > > To replicate behavior, create new db object (db = SQLDB('sqlite....., ) > > > > and define table. The database admin does not insert any rows, nor can > > > > any statements from controller. > > > > > Vihang --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
