On Wed, 26 Jul 2006 16:02:00 -0500, Dennis Jenkins wrote: >[EMAIL PROTECTED] wrote: >> It has been suggested that I add a mutex to every SQLite >> database connection. This would cause access to a database >> connection to automatically serialize even when two or more >> threads try to use that connection at once, thus preventing >> problems such as the above. >> >> The downside is the (minimal) additional overhead of acquiring >> and releasing a mutex on each API call. There will also be >> some changes to the OS-layer backend which will break >> private ports to unusual OSes. >> >> Thoughts? >> >> -- >> D. Richard Hipp <[EMAIL PROTECTED]>
>IMHO: > >Don't do it. Those of us that want to use threads should create our own >threaded sqlite wrappers. If i understand Richard well, there would be a mutex for serializing calls to the same database connection. So nothing would change if each thread opened its own instance. As it doesn't affect my applications in any way I'm not particularly in favour or against it, but i can imagine that life would be easier for many other people if such a feature were available. In order to keep sqlite lean and mean where needed I think it should be a compile time option. -- ( Kees Nuyt ) c[_]
