Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of daevaorn@gmail.com designates
 209.85.218.221 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type;
        b=hS+1hV1L1LBIePTaJmh2UFbaxS7AquX9Dz9Q8A+mFHaWxyREVdVMrqz/v7rHhhphJL
         h0H96pchIuxvFbxFric1PCKLZY95dqKUCklLvTaQ85Z4GrJmj9Ty0I84tEUcyPRAS1Hr
         GaEYVirUJQ9ABoZkAqPBZn68l3JndRM/7TsXU=
MIME-Version: 1.0
From: Alex Koshelev <daevaorn@gmail.com>
Date: Wed, 24 Mar 2010 04:23:08 +0300
Message-ID: <e3794dc91003231823k3197e3eav122a0e12fc60f716@mail.gmail.com>
Subject: CouchDB's ACID compliance
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

Hi, all!

I'm digging into CouchDB for my work and I want to understand better
its architecture and underlying concepts.

All sources over Internet (including Wikipedia [1]) describe ACID as
properties of database _transactions_. As we now CouchDB has no
transaction support in classing DB meaning -- there is no way to
execute several API calls (DB operations) even with Bulk API in atomic
way.

But CouchDB documentation [2] and many sources say that it is ACID compliant.

I understand that as ACID can be applied to individual API calls (for
example PUT or POST to some document) in the meaning that
_transaction_ is the set of low level CouchDB server operations from
parsing of http requests to data flushing on disk. And it can be
treated
as ACID requirements compatibility.

Am I right? Or ACID compliance with CouchDB means something different.

Thanks.

[1]: http://en.wikipedia.org/wiki/ACID
[2]: http://couchdb.apache.org/docs/overview.html
---
Alex Koshelev