couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Couchdb Wiki] Update of "How_to_intercept_document_updates_and_perform_additional_server-side_processing" by karmi
Date Fri, 08 Jan 2010 10:23:50 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.

The "How_to_intercept_document_updates_and_perform_additional_server-side_processing" page
has been changed by karmi.
The comment on this change is: Clarifiyng the purpose of _update functions.
http://wiki.apache.org/couchdb/How_to_intercept_document_updates_and_perform_additional_server-side_processing?action=diff&rev1=3&rev2=4

--------------------------------------------------

  
  == Usage ==
  
- To invoke a handler, one must "PUT" the document against the handler function itself (POST
does not seem to be supported). Using the canonical document URL won't invoke any handlers.
For example, to invoke the "in-place" handler defined above, the URL to use is:
+ To invoke a handler, one must "PUT" the document against the handler function itself (POST
does not seem to be supported). Using the canonical document URL won't invoke any handlers.
+ 
+ For example, to invoke the "in-place" handler defined above, the URL to use is:
  
  {{{
  http://127.0.0.1:5984/<my_database>/_design/<my_designdoc>/_update/in-place/<mydocId>?field=title&value=test
  }}}
  
- This usage seems to indicate that unlike document validators, the user's intend must be
clear by calling an individual handler explicitly.
+ This means that unlike document validators, the user's intent must be clear by calling this
individual handler explicitly. In this sense, you should think about an ''_update'' handler
as complementary to ''_show'' functions, not to ''validate_doc_update'' functions.
  

Mime
View raw message