couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Hendricks <mich...@ndrix.org>
Subject Re: json term changes
Date Thu, 28 Aug 2008 03:43:09 GMT
On Wed, Aug 27, 2008 at 04:17:09PM -0400, Damien Katz wrote:
> I've checked in the json_term_changes branch today. Big thanks to Chris 
> Anderson (jchris) as this is mostly his work.

Running the json_term_changes branch, GET http://localhost:5984/
returns:

    {"couchdb":[87,101,108,99,111,109,101],"version":[48,46,57,46,48,97,54,56,57,55,48,55,45,105,110,99,117,98,97,116,105,110,103]}


Another regression that I noticed is that POSTing a single document to
_bulk_docs does not create a unique ID for the document.  For example:

---- Request ----
POST http://localhost:5984/net-couchdb-11383-21716/_bulk_docs
Accept: application/json

{"docs":[{"foo":"bar"}]}

---- Response ----
HTTP/1.1 201 Created
Cache-Control: must-revalidate
Date: Thu, 28 Aug 2008 03:39:07 GMT
Server: CouchDB/0.9.0a689707-incubating (Erlang OTP/R12B)
Content-Length: 53
Content-Type: application/json
Client-Date: Thu, 28 Aug 2008 03:39:07 GMT
Client-Peer: 127.0.0.1:5984
Client-Response-Num: 1

{"ok":true,"new_revs":[{"id":"","rev":"1199132587"}]}


Notice that the "id" is the blank string.

-- 
Michael

Mime
View raw message