On 27 Sep 2011 at 00:19, Simon Slavin <slav...@bigfraud.org> wrote: > On 26 Sep 2011, at 11:32pm, Tim Streater wrote:
>> But, very often the database on which the error occurs is :memory: - and I >> guess each thread will have its own one of those. > > Are you doing concurrent access to your :memory: databases ? Looking back through my logs to early July, there were three instances - and in each case a housekeeping script is doing a VACUUM. So that's a strong pointer. And in the case of :memory:, it may just appear (to my ill-informed eyes) to be related to :memory:. The statement is in fact: insert into mem.messages select * from main.messages where absid= some value; Here, :memory: was attached as mem, and main was opened earlier but will be one of those that gets VACUUMed. I guess the select can then fail in the same way. -- Cheers -- Tim
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
