[COUCHDB-802] Doc ID should auto-generate if not provided, before sending to _update function [PATCH]

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.11
• Fix Version/s: 0.11.1
• Component/s: HTTP Interface, JavaScript View Server
• Labels: uuid

Environment

Linux

• Assignee: Unassigned
• Reporter: Jason Smith
• Created: 16/Jun/10 07:35
• Updated: 16/Jun/10 21:18
• Resolved: 16/Jun/10 21:18

Description

The main bug is this: _show and _update functions should be able to mimic the standard HTTP/JSON API. A common pattern people are moving to is rewriting to _show and _update, so the client thinks it is hitting normal couch, however additional logic happens (e.g. auto-timestamping).

Unfortunately, _update cannot return an auto-generated ID for POST to /db/_design/ddoc/_update. The semantics should match POST to /db/ – If an _id is provided, use that; otherwise auto-generate one. The best an _update function can do now is Math.random() or similar; however one loses the advantage of sequential UUID generation from couch's internals.

The fix is for couch to send a random UUID if the update URL did not include the final /Id component. The function itself in the view server can decide whether to use it. Assuming that change, the update function could at least be capable of duplicating the direct API using the following Javascript logic:

function(doc, req) {
if(doc && doc._id == req.id)

{ // To be pedantic, I could confirm req.method == "PUT" log("I am an update by id"); }

else if(doc === null && req.id) {
if(req.method == "POST")

{ log("I am a create, id was auto-generated"); }

else if(req.method == "PUT")

{ log("I am a create, id was supplied by client"); }

}
}