on a second thought. This could conflict with close_all_instances and needs some more thought.
On May 4, 5:13 pm, mdipierro <[email protected]> wrote: > we should and it should call > > self._connection.close() > > On May 4, 5:00 pm, Thadeus Burgess <[email protected]> wrote: > > > We do not have a db.close(). > > > However I figured the problem. In most other db systems (sqlalchemy, > > django, etc) use the ``sqlite://:memory:`` syntax, whereas web2py dal > > uses ``sqlite:memory:``. > > > However, db.close() would be helpful for external scripts like cron ? > > > -- > > Thadeus > > > On Tue, May 4, 2010 at 4:33 PM, mdipierro <[email protected]> wrote: > > > db.close() ? > > > > On May 4, 4:22 pm, Thadeus Burgess <[email protected]> wrote: > > >> More info: > > > >> I have an "sqlite://:memory:" dal connection. I am reusing this memory > > >> database for unit testing. > > > >> I need to completely remove the database on my def tearDown() function. > > > >> Something like > > > >> db._cursor.close() > > > >> However the database still seems to be in memory when I load it up again. > > > >> -- > > >> Thadeus > > > >> On Tue, May 4, 2010 at 3:58 PM, Thadeus Burgess <[email protected]> > > >> wrote: > > >> > I have a DAL instance that I want to tear down so the database becomes > > >> > unlocked. > > > >> > How can I accomplish this? > > > >> > -- > > >> > Thadeus
