incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henrik Skupin (JIRA)" <j...@apache.org>
Subject [jira] Created: (COUCHDB-886) Add option to set query options, defined in rewrites.json, as default
Date Mon, 13 Sep 2010 05:03:11 GMT
Add option to set query options, defined in rewrites.json, as default
---------------------------------------------------------------------

                 Key: COUCHDB-886
                 URL: https://issues.apache.org/jira/browse/COUCHDB-886
             Project: CouchDB
          Issue Type: Bug
          Components: Database Core
            Reporter: Henrik Skupin


With the latest version of CouchDB the URL parameters are not taken into account when the
rewrites.json file specifies the same ones for the appropriate entry. See the following example:

  {
    "from" : "/general/reports",
    "to" : "_list/general_reports/general_reportsByDate",
    "query" : {
      "descending" : true,
      "limit" : 51
    }
  }

default values: http://mozmill.hskupin.info/general/reports
custom values: http://mozmill.hskupin.info/general/reports?limit=10

Whether which URL you are loading, the values from rewrites.json are always used. Once the
limit entry gets removed from that file, the URL parameter is used and 10 rows are displayed.

As proposed by Benoit query entries should be explicitly allowed to have a default value.
Otherwise the value from rewrites.json has the priority.

"query": {
 "key": { "value": ":var", "default": 1}
}

Can true be used instead of a number? It could be confusing this way, especially when the
value is also a number.

-- 
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