I was wondering if anyone here had any comments on this thread on the
Python TurboGears group:
Essentially, people are getting a Database is locked error from the ORM
(SQLObject). The recommendation seems to be "Don't use SQLite".
I am seeing this
I have actually done that and it works well for a particular class of
applications, ones with a relatively small number of simultaneous users.
For large numbers we switch to PostgreSQL The basic architecture of
Sqlite, and why it is "Lite", is that it uses a single file and file
I was afraid of that...it would be cool if someone created a sqlite
handled the networking and serialization...I would take a crack at it
right now I don't have time.
Dan Kennedy wrote:
I had a musing while reading:
> I had a musing while reading:
> where it reminded me of one of MySQL's features:
> MySQL's database is built so that it can use a range of different
> storage mechanisms, tuned for different
- Original Message -
From: "Christian Smith" <[EMAIL PROTECTED]>
Sent: Thursday, April 20, 2006 11:16 AM
Subject: Re: [sqlite] Using sqlite3_open or sqlite3_open16?
> On Thu, 20 Apr 2006, DBTools Software wrote:
> >I have an
Mail list logo