incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Garvin <...@thegarvin.com>
Subject Re: Setting document _id in _update handler
Date Sat, 06 Mar 2010 07:58:40 GMT
Here's a fix for COUCHDB-645<http://issues.apache.org/jira/browse/COUCHDB-645>
:

http://github.com/coderifous/couchdb/tree/updates_handler_fix_COUCHDB_645

Is there a process for submitting patches?

Regards,
Jim


On Tue, Mar 2, 2010 at 5:38 PM, Jim Garvin <jim@thegarvin.com> wrote:

> I've got a patch coming for this.  Just need to write tests for it.  First
> contribution!  *woot*
>
>
> On Tue, Mar 2, 2010 at 4:53 PM, Jim Garvin <jim@thegarvin.com> wrote:
>
>> Hi again,
>>
>> Does anyone know a server-side workaround for this bug<https://issues.apache.org/jira/browse/COUCHDB-645>
>> ?
>>
>> Apparently if you use an _update handler for creating a document you are
>> responsible for the _id because CouchDB won't set it to a UUID if you just
>> leave it undefined. :'(
>>
>> Here's my update handler for reference:
>>
>> function(doc, req) {
>>   var newDoc = JSON.parse(req.body);
>>   newDoc.created_at = (new Date()).getTime();
>>   // newDoc._id = "is there a function I can call here to generate a
>> UUID?";
>>   return [newDoc, "ok"];
>> }
>>
>> Thanks,
>> Jim
>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message