R S wrote:
Hi Richard,
Thanks for your answers,
On Thu, 07 Oct 2004 11:35:08 -0400, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
R S wrote:
Another novice question:
Does this run in its separate process or is directly linked into the
application requiring access to the stored data.
It is a subroutine in your code.
So if my embedded system spawns many processes and each needs to talk
to the DB, is that possible?
Yes. As many different processes as you want can read the database
at the same time. Only one process at a time can write, but since
writes usually take a millisecond or less, that is not normally a
problem. The writer process does its writing, then when it is done
the other reader processes go back to doing their reading.
I don't want a crash in any of my embedded modules to crash the
database as well.
It won't. SQLite takes great care to protect the database even
if there is a crash or power failure.
What I meant was that the DB never crashes but is always running,
There is no separate server to "crash" and go down. Each process
reads and writes directly to the disk (or flash, probably, in your
case). If one process dies, there is nothing to prevent the others
from continuing to access the database file.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
