couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <>
Subject Re: couchdb transactions changes
Date Mon, 09 Feb 2009 13:47:04 GMT

On 9 Feb 2009, at 13:38, Antony Blakey wrote:
>> Antony, those sounds like interesting ideas, and I hope you can get  
>> it working. But a one-way replicable db with full-consistency  
>> guarantees is not what CouchDB was ever intended to be (to be  
>> clear, this is a statement of fact). I don't disapprove of it, but  
>> it doesn't fit with CouchDB's design. I'm also not convinced of the  
>> utility of it in the general case, the one-way replication  
>> limitation to me doesn't solve interesting problems, but that's  
>> just my opinion.
> [...]
> And if my assumption about the ordering of replication records is  
> correct, I'd like to see a commit # in the rev because that enables  
> replication that would preserve an ACID bulk_docs contract in  
> exclusive replication scenarios.

The question is wether you are willing to drive the coding effort and
community communication to make that happen. Like Damien, I'm not
trying to discourage you, on the contrary, I'd love to see the community
driving features.


View raw message