> The restriction is due to a bug found in many versions of Linux > (ex: Redhat 9) which prevents a fcntl lock created in one thread > from being removed or modified in a different thread. Since > SQLite uses fcntl-locks for concurrency control, running SQLite > on a system that has the bug would lead to corrupt databases. > For the sake of portability, therefore, SQLite requires that a > database connection always be used from the same thread > where it was created.
So I am correct in thinking that I *must* use a different DB backend if I want to run anything more than the development server? This is a small intranet app and I had started out hoping to keep the stack as simple as possible. Now I am using Apache+PostgreSQL, which is great except for the overhead and looming deadlines. So anyway, is it a reasonable assertion that if the app is actually to have more than 1 user--and in fact if it is going to run with Apache--then SQLite is right out? Thanks, David S.
