Yeah I gathered that but I found some django code that seemed to deal with that:
http://code.djangoproject.com/ticket/2658 I wasn't sure what the implications of this would be in a live situation. On Nov 29, 11:05 am, Javier Guerra Giraldez <jav...@guerrag.com> wrote: > On Mon, Nov 29, 2010 at 10:10 AM, Subsume <subs...@gmail.com> wrote: > > Right now I've got the name :memory: but the table always seems to be > > empty, despite objects being created. > > from the docs (http://www.sqlite.org/inmemorydb.html): > > > Every :memory: database is distinct from every other. So, opening two > > database connections each with the filename ":memory:" will create two > > independent in-memory databases. > > -- > Javier -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
