Mikeal Rogers wrote: > > Excuse me for being very dense here, but I'm missing what's going on > > here. You found a problem with in-memory SQLite and then did or didn't > > solve it? Or you just worked around it? > > Sorry for the confusion. > > I worked around it. It's still an outstanding issue, I'm not that > familiar with the differences between using an in memory database and > using regular sqlite and have hit my limit on being able to track it.
I'd bet this is related to some issues I've seen in trying to get the multi-db branch tests passing post r3661. The trouble is (or seems to me to be) that anything that uses the test client causes the request_finished signal to fire, which causes connection.close() to be called, which makes the in-memory database go away, or at least lose all of the tables, etc, that were populated into it during the "request". JP --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
