Eugene Lazutkin wrote:
It looks pretty much like the patch #463, which fixed multi-threading
problem for MySQL. AFAIR, somebody ported it to PostGres.
That was me: http://code.djangoproject.com/ticket/900
However the patch there wasn't included (yet?).
Now sqlite has similar problem. Maybe w
David S. wrote:
No, trac for example uses sqlite, too and it runs fine. I don't know
about this particular behaviour, but maybe the sqlite faq will give you
some answers about that.
Are you creating a thread in your app that makes changes on your database ?
I am just using the Django ORM.
> No, trac for example uses sqlite, too and it runs fine. I don't know
> about this particular behaviour, but maybe the sqlite faq will give you
> some answers about that.
> Are you creating a thread in your app that makes changes on your database ?
I am just using the Django ORM.
But I did fi
David S. wrote:
> 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?
No, trac for example uses sqlite, too and it runs fine. I don't know
about this particular behaviour,
> 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
David S. wrote:
> Anyone familiar with this error running Apache and SQLite?
>
> SQLite objects created in a thread can only be used in that same thread
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 re
Anyone familiar with this error running Apache and SQLite?
SQLite objects created in a thread can only be used in that same thread
7 matches
Mail list logo
