couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Couchdb Wiki] Update of "ApiVueHttp" by BenoitC
Date Sun, 29 Jun 2008 09:49:46 GMT
Dear Wiki user,

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

The following page has been changed by BenoitC:

The comment on the change is:
traduction démarrée

New page:
#language fr

Introduction sur l'API vue HTTP de CouchDB.

== Bases ==

Les vues sont l'outil de base pour interroger et reporter des documents CouchDB.

Les vues sont définies avec des fonctions Javascript. Voici une fonction très simple :

function(doc) {
  emit(null, doc);

Voir ["Vues"] pour plus d'informations.

== Creating Views ==

To create a permanent view, the functions must first be saved into special ''design documents''.
The IDs of design documents must begin with ''_design/'' and have a special views attribute
that have a ''map'' member and an optional ''reduce'' member to hold the view functions. All
the views in one design document are indexed whenever any of them gets queried.

A design document that defines ''all'', ''by_lastname'', and ''total_purchases'' views might
look like this:

  "language": "javascript",
    "all": {
      "map": "function(doc) { if (doc.Type == 'customer')  emit(null, doc) }"
    "by_lastname": {
      "map": "function(doc) { if (doc.Type == 'customer')  emit(doc.LastName, doc) }"
    "total_purchases": {
      "map": "function(doc) { if (doc.Type == 'purchase')  emit(doc.Customer, doc.Amount)
      "reduce": "function(keys, values) { return sum(values) }"

The ''language'' property tells CouchDB the language of the view functions, which it uses
to select the appropriate ViewServer (as specified in your couch.ini file). The default is
to assume Javascript, so this property can be omitted for Javascript views.

== Altering/Changing Views ==

To change a view or multiple view just alter the document (see HttpDocumentApi) they are stored
in and save it as a new revision.

== Access/Query ==

Once this document is saved into a database, then the ''all'' view can be retrieved at the



GET /some_database/_view/company/all HTTP/1.0
Date: Thu, 17 Aug 2006 05:39:28 +0000GMT

And will result in the following response:

 HTTP/1.1 200 OK
 Date: Thu, 17 Aug 2006 05:39:28 +0000GMT
 Content-Length: 318
 Connection: close

    "total_rows": 3,
    "offset": 0,
    "rows": [{
        "key": null,
        "value": {
          "Address":"2407 Sawyer drive, Charlotte NC",
      }, {
        "key": null,
        "value": {
          "Address":"123 Fake st., such and such",
      }, {
        "key": null,
          "Address":"1234 Fake st., such and such",

== Ad Hoc Views ==

One-off queries (eg. views you don't want to save in the CouchDB database) can be done via
the special view ''_temp_view'':

POST /some_database/_temp_view  HTTP/1.0
Content-Length: 48
Date: Mon, 10 Sep 2007 17:11:10 +0200
Content-Type: application/json

  "map" : "function(doc) { if ('bar') { emit(null,; } }"


Could result in the following response:

  "total_rows": 1,
  "offset": 0,
  "rows": [{
      "id": "AE1AD84316B903AD46EF396CAFE8E50F",
      "key": null,
      "foo": "bar"

== Querying Options ==

Columns can be a list of values, there is no set limit to the number of values or amount of
data that columns can hold.

The following URL query arguments are allowed:

  * key=keyvalue
  * startkey=keyvalue
  * startkey_docid=docid
  * endkey=keyvalue
  * count=max rows to return
  * update=false
  * descending=true
  * skip=rows to skip

''key'', ''startkey'', and ''endkey'' need to be properly JSON encoded values (for example,
startkey="string" for a string value).

If you specify ''?count=0'' you don't get any data, but all meta-data for this View. The number
of documents in this View for example. If ''count'' is specified as a negative number, you
will receive that many documents prior to the specified ''startkey''.

The ''skip'' option should only be used with small values, as skipping a large range of documents
this way is inefficient (it scans the index from the startkey and then skips N elements, but
still needs to read all the index values to do that). For efficient paging use ''startkey''
and/or ''startkey_docid''.

The ''update'' option can be used for higher performance at the cost of possibly not seeing
the all latest data. If you set the ''update'' option to ''false'', CouchDB will not perform
any refreshing on the view that may be necessary.

View rows are sorted by the key; specifying ''descending=true'' will reverse their order.
Note that the ''descending'' option is applied before any key filtering, so you may need to
swap the values of the ''startkey'' and ''endkey'' options to get the expected results. The
sorting itself is described in ViewCollation.

== Debugging Views ==

When creating views, CouchDB will check the syntax of the submitted JSON, but the view functions
themselves will not be syntax checked by the Javascript interpreter. And if any one of the
view functions has a syntax error, none of the view functions in that design document will
execute. Perhaps test your functions in a temporary view before saving them in the database.

As of r660140 there is a log function available in the views, which logs to the couch.log.
It can be helpful for debugging but hinders performance, so it should be used sparingly in
production systems.

  "map": "function(doc) { log(doc); }"

View raw message