Randall Smith wrote: > A shared-cache, in-memory database is "persistent" across connections > from the same process that do not overlap in time?
No. <http://www.sqlite.org/inmemorydb.html#sharedmemdb> says: | The database is automatically deleted and memory is reclaimed when the | last connection to the database closes. > ... when I re-run the unit test, the data in the in-memory DB seems > to still be around > [...] > Is there some way to reliably blow away one of these databases so I > know there will be no hangover state after that operation and can > start fresh with a virgin database? Tell your unit test framework to blow away the connection(s). Regards, Clemens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
