Hi Edwin,

> i'm now wondering as to what extent ACID properties are implemented in
> the picolisp DB implementation.

All processes operating on a database at a given time are children of a
common parent process. If they use the database functionality in the
recommended standard way (e.g. via the GUI), then ACID properties should
be preserved.

Some key functions are "http://software-lab.de/doc/refD.html#dbSync";,
"http://software-lab.de/doc/refC.html#commit"; and related functions
which build upon them like 'put!>' etc. (see
"http://software-lab.de/doc/refE.html#entityMesssages";).

These mechanisms synchronize transactions between the involved
processes. So far about "Atomicity" and " Consistency". Concerning
"Isolation" it is handled by using separate processes, and for
"Durability" matters, the database can be opened in certain
modes which involve transaction logs and mirroring schemes
(see "http://software-lab.de/doc/refP.html#pool";).

I hope these fragments of information help you for the moment. Please
feel free to ask about details.

Cheers,
- Alex
-- 
UNSUBSCRIBE: mailto:picol...@software-lab.de?subject=unsubscribe

Reply via email to