You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Benjamin Young (Commented) (JIRA)" <ji...@apache.org> on 2011/10/06 02:06:29 UTC
[jira] [Commented] (COUCHDB-1303) Add a _bulk_update handler
similar to _update but for bulk document changes
[ https://issues.apache.org/jira/browse/COUCHDB-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121623#comment-13121623 ]
Benjamin Young commented on COUCHDB-1303:
-----------------------------------------
Others have hit this situation as well: http://stackoverflow.com/questions/4061766/couch-db-bulk-update-using-handlers/7669106
> Add a _bulk_update handler similar to _update but for bulk document changes
> ---------------------------------------------------------------------------
>
> Key: COUCHDB-1303
> URL: https://issues.apache.org/jira/browse/COUCHDB-1303
> Project: CouchDB
> Issue Type: New Feature
> Reporter: Benjamin Young
> Labels: api, update_request_handler
>
> _update handlers are great (and getting better!) for building RESTful API's inside CouchDB. One limitation I found tonight is that _update can only do a single document at a time. If the API I'm building needs to update multiple docs (in a similar fashion to _bulk_docs), then an outside "proxy" script is required. It would be ideal to have a _bulk_update handler to allow for the same functionality as _update, but with the ability to insert multiple documents at once.
> Perhaps the current _update handler API could be extended to support multiple IDs/documents, but a separate API endpoint would be seem reasonable if needed.
> Thanks for considering this idea.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Created] (COUCHDB-1303) Add a _bulk_update handler
similar to _update but for bulk document changes
Posted by Benoit Chesneau <bc...@gmail.com>.
On Thursday, October 6, 2011, Benjamin Young (Commented) (JIRA) <
jira@apache.org> wrote:
>
> [
https://issues.apache.org/jira/browse/COUCHDB-1303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121623#comment-13121623]
>
> Benjamin Young commented on COUCHDB-1303:
> -----------------------------------------
>
> Others have hit this situation as well:
http://stackoverflow.com/questions/4061766/couch-db-bulk-update-using-handlers/7669106
>
>> Add a _bulk_update handler similar to _update but for bulk document
changes
>>
---------------------------------------------------------------------------
>>
>> Key: COUCHDB-1303
>> URL: https://issues.apache.org/jira/browse/COUCHDB-1303
>> Project: CouchDB
>> Issue Type: New Feature
>> Reporter: Benjamin Young
>> Labels: api, update_request_handler
>>
>> _update handlers are great (and getting better!) for building RESTful
API's inside CouchDB. One limitation I found tonight is that _update can
only do a single document at a time. If the API I'm building needs to update
multiple docs (in a similar fashion to _bulk_docs), then an outside "proxy"
script is required. It would be ideal to have a _bulk_update handler to
allow for the same functionality as _update, but with the ability to insert
multiple documents at once.
>> Perhaps the current _update handler API could be extended to support
multiple IDs/documents, but a separate API endpoint would be seem reasonable
if needed.
>> Thanks for considering this idea.
>
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
I would really prefer to sit down a little and start to rethink the couchapp
engine. Restful means imo that on a particular resource we could react on
each actions (here HTTP verbs). Instead we did the same error Rails did by
having a resource per actions or so. Bulk updates would be another hack
around this so I'm -1 on such features. New ticket about what i would like
to design is coming along.