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
I’m not sure if this is what you’re after, but from what I understand you’re looking for the [JsonIgnore] attribute. Stops properties from being serialized with the rest of the object into to JSON. [JsonIgnore] public string Whatever{ get; set; }
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
Ok, figured it out, if anyone interested: get deleted history, e.g.: curl http://example.iriscouch.com/test/_changes you’ll see deleted documents with $id and $rev, put empty document as new version, e.g.: curl -X PUT http://example.iriscouch.com/test/$id?rev=$rev -H “Content-Type: application/json” -d {} now you can get all revisions info, e.g: curl http://example.iriscouch.com/test/$id?revs_info=true obtain version before deletion, e.g.: curl http://example.iriscouch.com/test/$id?rev=$prev_rev put … 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
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
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
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
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
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