couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Skelton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-338) key, startkey, endkey query args passed to list function as strings, not JSON
Date Wed, 29 Apr 2009 00:56:30 GMT

    [ https://issues.apache.org/jira/browse/COUCHDB-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703926#action_12703926
] 

Andy Skelton commented on COUCHDB-338:
--------------------------------------

Ran Test Suite against Futon on Apache CouchDB  0.10.0a769507 with patch applied. All success.

> key, startkey, endkey query args passed to list function as strings, not JSON
> -----------------------------------------------------------------------------
>
>                 Key: COUCHDB-338
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-338
>             Project: CouchDB
>          Issue Type: Bug
>         Environment: trunk @769507
>            Reporter: Andy Skelton
>            Priority: Minor
>         Attachments: query_to_json_terms.diff
>
>
> In list function, req.query.[key|startkey|endkey] are strings such as "[\"foo\"]" instead
of JSON such as ["foo"]. When constructing paging URLs using req.query.endkey, this argument
is escaped once for each page traversal. The paging continues to work, but the URLs get longer
and longer:
> endkey=["cat",null]
> endkey="[\"cat\",null]"
> endkey="\"[\\\"cat\\\",null]\""
> Attached patch applies ?JSON_DECODE to these query arguments.

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