You need to think of how you approach the application in a document oriented way. If you simply try to replicate how you would model the problem in an RDBMS then you will fail. There are also different trade-offs that you might want to make. ([ed: not sure how this ties into the argument but:] … Read more
First, you need to create your index. I suggest that you create an index on the Calibration.Presettings.Date field. You can use the following JSON object to create it: { “index”: { “fields”: [ “_id”, “Calibration.Presettings.Date.[].Type” ] }, “type”: “json” } So the selector would be like this : { “selector”: { “Calibration.Presettings.Date”: { “$elemMatch”: { … Read more
The example function in-place is not the same as “in-place” updates in other databases. CouchDB still uses an append-only architecture; document update handlers still create a new doc revision, etc. Still, update handlers are quite convenient and worth learning. Suppose you have a document with an accumulator. You want to accumulate an integer in a … Read more
Here’s a quote from a recent blog post from Dare Obasanjo. SQL databases are like automatic transmission and NoSQL databases are like manual transmission. Once you switch to NoSQL, you become responsible for a lot of work that the system takes care of automatically in a relational database system. Similar to what happens when you … Read more
According to Express res.send([body]) docs: The body parameter can be a Buffer object, a String, an object, or an Array You can’t send a number by itself. Try either converting the number to a string res.send(”+result.rows[0].doc.imdb.rating); or send it as an object value res.send({ result: result.rows[0].doc.imdb.rating});
The CouchDB Guide has a good discussion of pagination, including lots of sample code, here: http://guide.couchdb.org/draft/recipes.html#pagination Here’s their algorithm: Request rows_per_page + 1 rows from the view Display rows_per_page rows, store last row as next_startkey As page information, keep startkey and next_startkey Use the next_* values to create the next link, and use the others … Read more
FormData will always be sent as multipart/form-data. If you just post normal form data without uploading files, multipart/form-data is better. If you want to upload files, multipart/form-data is better. If you have to upload files with x-www-form-urlencoded, you should convert the files data to string data via base64 etc, and write special server-end code. This … Read more
Finally we can solve this problem easily using JSONModel. This is the best method so far. JSONModel is a library that generically serialize/deserialize your object based on Class. You can even use non-nsobject based for property like int, short and float. It can also cater nested-complex JSON. Considering this JSON example: { “accounting” : [{ … Read more
I think there are some essential differences between CouchDB and Couchbase Server that need to be pointed out. I will not write about the advantages of switching from CouchDB to the Couchbase Server because those are described pretty much everywhere (see The Future of CouchDB by Damien Katz or Couchbase vs. Apache CouchDB by Couchbase). … Read more
This community wiki page provides links to some SQL patterns showing how they may be implemented in Cloudant. As this is a community wiki feel free to add new Q&A links here. General database queries Joining two documents by key? How do I do the SQL equivalent of “DISTINCT” in CouchDB? How do I do … Read more