couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Carter (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-645) _update: document created with undefined _id
Date Tue, 28 Dec 2010 23:37:46 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975680#action_12975680
] 

Christian Carter commented on COUCHDB-645:
------------------------------------------

It might be more appropriate for the new document _id to be that of the UUID that was passed
in the request object, so a response can be generated in the update function and still be
able to reference the new document path....

> _update: document created with undefined _id
> --------------------------------------------
>
>                 Key: COUCHDB-645
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-645
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 0.11
>         Environment: Linux, CouchDB built from HEAD
>            Reporter: Cliff Stanford
>            Assignee: Chris Anderson
>         Attachments: updates_handler.patch
>
>
> Using an update handler, if a document is returned with  {  _id : undefined }, the document
will be created on the database with an undefined _id and will henceforth not be accessible
to modify or delete although it will show up in views.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message