You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Bob Clary <bo...@bclary.com> on 2010/07/15 12:29:08 UTC

changes to list function's req.query in CouchDB 1.0.0

Previously in CouchDB 0.11 calling a list function with query strings 
passed the query strings as properties of the req.query object with the 
property name being the query string parameter name and the value being 
a string containing the query string parameter value.

For example:

?include_docs=true&startkey={"foo":"bar"}&filter={"before":"2010-07-14T"}

would give:

req.query =
{
     include_docs: 'true',
     startkey: '{"foo":"bar"}',
     filter:   '{"before":"2010-07-14T"}'
}

while:

?include_docs=true&startkey=["foo","bar"]&filter={"before":"2010-07-14T"}

would give:


req.query =
{
     include_docs: 'true',
     startkey: '["foo", "bar"]',
     filter:   '{"before":"2010-07-14T"}'
}

Now in CouchDB 1.0.0 the I get the JSON.parse'd values of the startkey, 
endkey, and key.

For example

?include_docs=true&startkey={"foo":"bar"}&filter={"after":"2010-07-14T"}

gives

req.query =
{
     include_docs: 'true',
     startkey: {"foo":"bar"},
     filter:   '{"after":"2010-07-14T"}'
}

while

?include_docs=true&startkey=["foo","bar"]&filter={"after":"2010-07-14T"}

gives

req.query =
{
     include_docs: 'true',
     startkey: ["foo", "bar"],
     filter:   '{"after":"2010-07-14T"}'
}

I couldn't find any documentation about the change. Is this intended and 
will it continue to be the case going forward?

bc

Re: changes to list function's req.query in CouchDB 1.0.0

Posted by Noah Slater <ns...@apache.org>.
Can you clarify what change you think needs to be made to the downloads page?

On 15 Jul 2010, at 18:58, Bob Clary wrote:

> On 7/15/10 10:01 AM, Markus Jelsma wrote:
>> It should also be mentioned on the downloads page. Older versions also link to `backward incompatible changes`.
> 
> I did the wiki <http://wiki.apache.org/couchdb/Breaking_changes#Breaking_Changes>, but don't have access to the downloads page.


Re: changes to list function's req.query in CouchDB 1.0.0

Posted by Bob Clary <bo...@bclary.com>.
On 7/15/10 10:01 AM, Markus Jelsma wrote:
> It should also be mentioned on the downloads page. Older versions also link to `backward incompatible changes`.

I did the wiki 
<http://wiki.apache.org/couchdb/Breaking_changes#Breaking_Changes>, but 
don't have access to the downloads page.

RE: Re: changes to list function's req.query in CouchDB 1.0.0

Posted by Markus Jelsma <ma...@buyways.nl>.
It should also be mentioned on the downloads page. Older versions also link to `backward incompatible changes`.  
 
-----Original message-----
From: J Chris Anderson <jc...@gmail.com>
Sent: Thu 15-07-2010 17:57
To: user@couchdb.apache.org; 
Subject: Re: changes to list function's req.query in CouchDB 1.0.0


On Jul 15, 2010, at 3:29 AM, Bob Clary wrote:

> Previously in CouchDB 0.11 calling a list function with query strings passed the query strings as properties of the req.query object with the property name being the query string parameter name and the value being a string containing the query string parameter value.
> 
> For example:
> 
> ?include_docs=true&startkey={"foo":"bar"}&filter={"before":"2010-07-14T"}
> 
> would give:
> 
> req.query =
> {
>    include_docs: 'true',
>    startkey: '{"foo":"bar"}',
>    filter:   '{"before":"2010-07-14T"}'
> }
> 
> while:
> 
> ?include_docs=true&startkey=["foo","bar"]&filter={"before":"2010-07-14T"}
> 
> would give:
> 
> 
> req.query =
> {
>    include_docs: 'true',
>    startkey: '["foo", "bar"]',
>    filter:   '{"before":"2010-07-14T"}'
> }
> 
> Now in CouchDB 1.0.0 the I get the JSON.parse'd values of the startkey, endkey, and key.
> 
> For example
> 
> ?include_docs=true&startkey={"foo":"bar"}&filter={"after":"2010-07-14T"}
> 
> gives
> 
> req.query =
> {
>    include_docs: 'true',
>    startkey: {"foo":"bar"},
>    filter:   '{"after":"2010-07-14T"}'
> }
> 
> while
> 
> ?include_docs=true&startkey=["foo","bar"]&filter={"after":"2010-07-14T"}
> 
> gives
> 
> req.query =
> {
>    include_docs: 'true',
>    startkey: ["foo", "bar"],
>    filter:   '{"after":"2010-07-14T"}'
> }
> 
> I couldn't find any documentation about the change. Is this intended and will it continue to be the case going forward?

Yes, this will continue going forward -- do you mind adding it to the Breaking_changes page on the wiki?

Thanks

Chris



Re: changes to list function's req.query in CouchDB 1.0.0

Posted by J Chris Anderson <jc...@gmail.com>.
On Jul 15, 2010, at 9:26 AM, Bob Clary wrote:

> On 7/15/10 8:56 AM, J Chris Anderson wrote:
> 
>>> 
>>> I couldn't find any documentation about the change. Is this intended and will it continue to be the case going forward?
>> 
>> Yes, this will continue going forward -- do you mind adding it to the Breaking_changes page on the wiki?
> 
> Chris,
> 
> Sure. Do you know if this was in 0.11.1 or only 1.0.0 ?
> 

yes, this bugfix was applied to the 0.11.x branch as well.

Thanks!
Chris

> bc


Re: changes to list function's req.query in CouchDB 1.0.0

Posted by Bob Clary <bo...@bclary.com>.
On 7/15/10 8:56 AM, J Chris Anderson wrote:

>>
>> I couldn't find any documentation about the change. Is this intended and will it continue to be the case going forward?
>
> Yes, this will continue going forward -- do you mind adding it to the Breaking_changes page on the wiki?

Chris,

Sure. Do you know if this was in 0.11.1 or only 1.0.0 ?

bc

Re: changes to list function's req.query in CouchDB 1.0.0

Posted by J Chris Anderson <jc...@gmail.com>.
On Jul 15, 2010, at 3:29 AM, Bob Clary wrote:

> Previously in CouchDB 0.11 calling a list function with query strings passed the query strings as properties of the req.query object with the property name being the query string parameter name and the value being a string containing the query string parameter value.
> 
> For example:
> 
> ?include_docs=true&startkey={"foo":"bar"}&filter={"before":"2010-07-14T"}
> 
> would give:
> 
> req.query =
> {
>    include_docs: 'true',
>    startkey: '{"foo":"bar"}',
>    filter:   '{"before":"2010-07-14T"}'
> }
> 
> while:
> 
> ?include_docs=true&startkey=["foo","bar"]&filter={"before":"2010-07-14T"}
> 
> would give:
> 
> 
> req.query =
> {
>    include_docs: 'true',
>    startkey: '["foo", "bar"]',
>    filter:   '{"before":"2010-07-14T"}'
> }
> 
> Now in CouchDB 1.0.0 the I get the JSON.parse'd values of the startkey, endkey, and key.
> 
> For example
> 
> ?include_docs=true&startkey={"foo":"bar"}&filter={"after":"2010-07-14T"}
> 
> gives
> 
> req.query =
> {
>    include_docs: 'true',
>    startkey: {"foo":"bar"},
>    filter:   '{"after":"2010-07-14T"}'
> }
> 
> while
> 
> ?include_docs=true&startkey=["foo","bar"]&filter={"after":"2010-07-14T"}
> 
> gives
> 
> req.query =
> {
>    include_docs: 'true',
>    startkey: ["foo", "bar"],
>    filter:   '{"after":"2010-07-14T"}'
> }
> 
> I couldn't find any documentation about the change. Is this intended and will it continue to be the case going forward?

Yes, this will continue going forward -- do you mind adding it to the Breaking_changes page on the wiki?

Thanks

Chris