couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Fwd: Ten reasons why couchdb is better than (off topic)
Date Sun, 04 Jan 2009 22:42:27 GMT
---------- Forwarded message ----------
From: lasizoillo <>
Date: Sun, Jan 4, 2009 at 8:15 AM
Subject: Re: Ten reasons why couchdb is better than (off topic)

2009/1/3 mobil <>:
> Ten reasons why couchdb is better than (off topic)
> Guys I wrote up a small list of reasons why i think couchdb is way
> bettter than mysql. Do let me know what you think

And only one thing to dislike it:

line 114 in disp_hotel
line 528 in update
line 839 in post
line 888 in _request
PreconditionFailed: ('conflict', 'Update conflict')

If you update the same register in a short period of time you get an
'Update conflict' exception. You can solve this issue slicing a
document in more documents or with a more complex (and maybe blocker)
client. A non blocking server isn't cheap.

Slicing a document not every times is easy. You can do a tricky joins
with the power of collation[1]. But joins are tricky and generates
secondary efects (complex or impossible querys).


Couchdb is great *in his application field* like any other storage
system. Relational DB are great in his application field, the error is
use Relational DB for everything. You can see Tokyo Cabinet, Durus,
PyTables, RRD Tools and a lot of tools to solve your concrete storage
issues. CouchDB isn't panacea, but it's really great ;-)

Excuse me poor english. I hope that the idea can be understandable.


> --
> Gpirate the top torrent search engine
> >

You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to
To unsubscribe from this group, send email to<>
For more options, visit this group at

Gpirate the top torrent search engine

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message