The problem with sqlite:memory is that you can have multiple apps
running under the same web2py installation. There is no way to have
multiple sqlite:memory and those apps do not probably want to share
the database. One would have to cache the sqlite:memory connection
then it may be faster to cache the sessions directly.
Massimo
On Apr 6, 10:43 am, Iceberg <iceb...@21cn.com> wrote:
> Mmm, SQLDB('sqlite:memory:') would be a most intuitive choice, it is a
> pity that it does not work. No wonder it was once introduced but soon
> "forgotten". :-)
>
> So let's wait Massimo to adjust MEMDB to work with cache.ram, or
> perhaps a dedicated RAMDB for it, or even SQLDB('ram://'). I am fine
> with whatever naming convension, but slightly prefer the last one. :-)
>
> On Apr6, 10:28pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > You cannot use sqlite:memory" because that connection is not
> > persistant. It is closed when the the page is served.
>
> > On Apr 6, 2:36 am, Markus Gritsch <m.grit...@gmail.com> wrote:
>
> > > This thread had the same topic:
>
> > >http://groups.google.com/group/web2py/browse_thread/thread/b587b14f45...
>
> > > and resulted in the same problems using sqlite:memory: :)
>
> > > Robin B suggested a 'RAMDB':
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
