Re: Maybe problems with Metakit 2.4.9.3

>Another problem with SQLite is, it only handles one writer while
>allowing multiple readers. That's the same as with Metakit (ok, you can
>have multiple database connections with one writer each, but that will
>end in file locking if I understand it's architecture correctly).

As far as I know, SQLite cannot handle multiple "writer" connections. My
understanding is that it is a single writer, supporting multiple readers; as
is metakit, I presume. SQLite has a small footprint, supports standard SQL,
and is easily extensible via C or C++. Ideal for embedded systems, personal
dbms, single user applications. I think it is the open source equivalent of
Microsoft's MSAccess without the builtin forms, reports, etc.

It has all the features of a robust database such as transaction
commit/rollback, lock resolution, etc.; but is not intended as a
transactional, multi-user dbms. That's where MySQL and Postgress come in.
For PyDS, I would suggest implementing with SQLite, initially, and building
on a port that supports other sql databases, such as is done by Roundup
http://roundup.sourceforge.net/doc-0.7/features.html, an issue management
solution written in Python, supporting multiple database implementations.

\louis