Just promise yourself that you will never try to map a relational data model to a NoSQL database like MongoDB or CouchDB… This is the most common mistake developers make when evaluating emerging tech. That approach is analogous to taking a car and trying to use it to pull your cart down the road like … Read more
No. CouchDB uses an “optimistic concurrency” model. In the simplest terms, this just means that you send a document version along with your update, and CouchDB rejects the change if the current document version doesn’t match what you’ve sent. It’s deceptively simple, really. You can reframe many normal transaction based scenarios for CouchDB. You do … Read more
Probably you shouldn’t 🙂 The second most obvious answer is you should use it if your data isn’t relational. This usually manifests itself in having no easy way to describe your data as a set of columns. A good example is a database where you actually store paper documents, e.g. by scanning office mail. The … Read more
None of the existing “NoSQL” database provides a reasonable implementation of something that could be named “fulltext search”. MongoDB in particular has barely nothing so far (matching using regular expressions is not fulltext search and searching using $in or $all operators on a keyword word list is just a very poor implementation of a “fulltext … Read more
Thank you! This is a great example to show off CouchDB 0.11’s new features! You must use the fetch-related-data feature to reference documents in the view. Optionally, for more convenient JSON, use a _list function to clean up the results. See Couchio’s writeup on “JOIN”s for details. Here is the plan: Firstly, you have a … Read more