Bug#326648: libsqlite3-0: database handles can't be shared among threads any more

2006-05-14 Thread Tomas Fasth
Hello Adeodato, Is the reason for filing this bug still valid? Otherwise, I would like to close it now. Regards, Tomas

Bug#326648: libsqlite3-0: database handles can't be shared among threads any more

2005-09-04 Thread Florian Weimer
* Adeodato Simó: > Also, I have no idea what's the case for Debian: "On some versions of > Linux, a thread is not able to override locks created by a different > thread in the same process." Does this depend on the kernel, on libc, > or on something else? This is probably the same problem

Bug#326648: libsqlite3-0: database handles can't be shared among threads any more

2005-09-04 Thread Florian Weimer
* Florian Weimer: > * Adeodato Simó: > >> Also, I have no idea what's the case for Debian: "On some versions of >> Linux, a thread is not able to override locks created by a different >> thread in the same process." Does this depend on the kernel, on libc, >> or on something else? > > This

Bug#326648: libsqlite3-0: database handles can't be shared among threads any more

2005-09-04 Thread Adeodato Simó
Package: libsqlite3-0 Version: 3.2.5-1 [debian-devel CCed because I'm asking for advice at the end.] Until sqlite 3.2.2, a database handle could be opened in one thread and used in another. In 3.2.5 this has been disabled, and upstream recommends to open a db handle for each handle; which