Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of hskupin@gmail.com designates
 209.85.216.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=an4CbUS3CLFkuEfaxwokTKma1qsNPYpZ5r7SYUOUgfKRX7lyCqVsSdIMaLLy2+Hx3o
         rogD7rzJ/EbOuhKuQNpdPU8J3T7TVCIXldclv+gooDKhBIu4+2cbpSissM41tbBZJMKJ
         Cy9hwaDiHztA6tBQ7Q5p2mDrCsdFjFFJzQGqI=
MIME-Version: 1.0
Date: Sun, 12 Sep 2010 00:35:03 -0700
Message-ID: <AANLkTim8a9CuPu+Eu9fG39FJgpu3S+1j6GXrKgWQ1CfX@mail.gmail.com>
Subject: Query parameters in rewrites.json not handled as default values
From: Henrik Skupin <hskupin@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=0016e644d5509b6fb404900b0479

--0016e644d5509b6fb404900b0479
Content-Type: text/plain; charset=UTF-8

Hi,

During this week while being at Couchcamp I have already talked to Chris and
we decided to follow-up on the topic in the mailing list.

With the latest version of CouchDB the URL parameters don't seem be 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 default values are always used. Once
the limit entry gets removed from the rewrites.json file, the URL parameter
is used and 10 rows are displayed.

IMO the values specified in rewrites.json should really be default ones and
should not override user defined values.

Henrik

--0016e644d5509b6fb404900b0479--