Consider a django SQLite DB for each of the machines or have a central "collection" server running somewhere that the various individual agents can talk to - a REST, XML-RPC, or so API. -joe
On 5/22/06, Kilian CAVALOTTI <[EMAIL PROTECTED]> wrote:
On Sunday 21 May 2006 21:26, Graham King wrote:> K
sis.lip6.fr
Received: from spip.lip6.fr (mailia [127.0.0.1])
by poleia.lip6.fr (8.13.3/jtpda-5.4+CB) with ESMTP id k4M8Q2cd006328
; Mon, 22 May 2006 10:26:02 +0200
From: Kilian CAVALOTTI <[EMAIL PROTECTED]>
Organization: LIP6
To: django-users@googlegroups.com
Subject: Re:
Kilian,
I does indeed say here that SQLite can handle concurrent transaction,
by queuing them up:
http://www.sqlite.org/faq.html#q7
You're not using an NFS share are you ? Apparently that would break it.
Are you running the app / script on each users machine, or on a web
server the
tfix) with ESMTP id 64F62767B3
for ; Sun, 21 May 2006 18:24:58 +0200
(CEST)
From: Kilian CAVALOTTI <[EMAIL PROTECTED]>
Organization: LIP6
To: django-users@googlegroups.com
Subject: SQLite concurrent access to database
Date: Sun, 21 May 2006 18:25:01 +0200
User-Agent: KMail/1.9.1
Mim
4 matches
Mail list logo
