It would be safe and efficient provided that you did not have a massive
load with many processes expecting simultaneous access. Just be careful
that your applications can gracefully handle the occasional lock state
and use transactions carefully. Don't design in queries which have a
long execution time. It is called "..lite" for a good reason.
JS
Dave Dyer wrote:
If I designed a sqlite database to be used by a bunch of independent
applications, for example a bunch of CGI scripts each of which
opened the database, did some processing, and exited, would
that be (a) safe (b) effecient ?