Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: 209.85.220.226 is neither permitted
 nor denied by domain of jchris@couch.io)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
Subject: Re: Testsuite: changes question
From: J Chris Anderson <jchris@couch.io>
In-Reply-To: <4BA103DE.2020009@zeromail.org>
Date: Wed, 17 Mar 2010 10:41:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <46E97A09-6027-4D3B-83AE-9D380723E53C@gmail.com>
References: <4B9F9406.90109@zeromail.org> <4BA103DE.2020009@zeromail.org>
To: dev@couchdb.apache.org


On Mar 17, 2010, at 9:31 AM, Lena Herrmann wrote:

> Am 16.03.10 15:21, schrieb Lena Herrmann:
>> Hi,
>>=20
>> the "changes" method in couch.js takes not only options, but also =
keys.
>> What are the keys for?
>=20
> Okay I figured out what keys for. But the "changes" method doesn't =
seem to work properly. When it is called with keys, like:
>=20
> db.changes({"since":"1"}, ["123"]);
>=20
> It is supposed to do a POST request. But only GET and HEAD are =
allowed, so I get a 405 here.
>=20
> Can someone tell me where to fix this or do it themselves .. thanks.
>=20

My guess is that the _changes handler was copied and pasted from the =
_all_docs_by_seq handler, which may have supported that feature. We =
should probably just remove the keys option from the JS client.

Chris

>=20
> Cheers, Lena
>=20
>=20