Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-Id: <42E1E336-66E6-4A26-AFB2-2C92D4BF564C@apache.org>
From: Jan Lehnardt <jan@apache.org>
To: dev@couchdb.apache.org
In-Reply-To: <20090803090423.GA8374@uk.tiscali.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: POST with _id
Date: Mon, 3 Aug 2009 13:10:42 +0200
References: <20090803090423.GA8374@uk.tiscali.com>


On 3 Aug 2009, at 11:04, Brian Candler wrote:

> Is there any reason why, if you POST a document to a database and that
> document has an "_id" member, why this is ignored and a server- 
> generated _id
> is used instead?
>
> $ curl -X PUT http://127.0.0.1:5984/sample
> {"ok":true}
> $ curl --data-binary '{"_id":"foo","bar":"baz"}' -X POST http://127.0.0.1:5984/sample
> {"ok 
> ":true,"id":"f38341efa1ca9bebc528b452aa036846","rev":"1-4165745669"}

The API for creating a named document is PUT /db/docid
POSTing to /db is "add to a collection and let the server
care about identity."


> This seems inconsisent with a POST to _bulk_docs
>
> $ curl --data-binary '{"docs":[{"_id":"foo","bar":"baz"}]}' -X POST http://127.0.0.1:5984/sample/_bulk_docs
> [{"id":"foo","rev":"1-1298018621"}]

Bulk docs is different API.

--

That's the reasons. Do you propose a change? :)

Cheers
Jan
--