Thanks for the answer. The bulk API is more for efficiency then transaction. Even if I use "transaction" on single node it is not guaranty that the same will be done on other nodes after replication and if I can't use replication there is no point in using CouchDB in the first place.
Ido On Sun, Dec 19, 2010 at 6:25 PM, Cliff Williams <[email protected]> wrote: > Ido, > > I hope you are well. > > have you had a look at > http://wiki.apache.org/couchdb/HTTP_Bulk_Document_API > > (the section labelled Transactional Semantics with Bulk Updates) > > best regards > > cliff > > > On 19/12/10 15:17, Ido Ran wrote: > >> Hi, >> I have application which the primary data model is a network (graph). >> Currently I use RDBMS in which I have table of Node and table of Link. The >> Link table has FromNode, ToNode and LinkType fields. >> >> What is a good document model to put this type of data in CouchDB? >> Should I provide information about my application that I didn't provide >> here? >> >> Since there are no transaction I fail to see how can I ensure that my data >> will not be corrupted? >> Also since there is no constraints, only validation function, which are >> not >> exactly the same because replication do not pass by them for clear >> reasons, >> is that mean I have always asume the data is not valid? >> >> Thank you, >> Ido >> >>
