Hi NIc,
I think the view API will always return the id field - however: you can
create a list function (same semantics: in a design doc have "lists":
instead of "views") and emit pretty much anything you like, including JSON
in whichever flavor
Best Regards
Sebastian
On Mon, May 5, 2014 at
Great, thanks, with
myview?startkey=["3566120224",{}]&endkey=["3566120224"]&descending=true
Is working now, but how can I get the view without the id field?
Nic
2014-05-05 15:51 GMT-04:00 Mike Marino :
> > Am 05.05.2014 um 21:46 schrieb Nicolas Palacios :
> >
> > Well I'm using the same keys
> Am 05.05.2014 um 21:46 schrieb Nicolas Palacios :
>
> Well I'm using the same keys for start and end..
You're using the object brackets {}, so they're not the same. Try
switching that to the startkey.
>
>
> 2014-05-05 15:24 GMT-04:00 Alexander Shorin :
>
>> On Mon, May 5, 2014 at 11:19 PM, Ni
Well I'm using the same keys for start and end..
2014-05-05 15:24 GMT-04:00 Alexander Shorin :
> On Mon, May 5, 2014 at 11:19 PM, Nicolas Palacios
> wrote:
> > Hi Jens, thanks for your comment.
> >
> > But if I try with:
> > myview?startkey=["3566120224"]&endkey=["3566120224",{}]&descending=tru
Indeed, it may be a bit quirky but if you do what it asks you should get what
you're looking for:
> myview?startkey=["3566120224",{}]&endkey=["3566120224"]&descending=true
That is, CouchDB always wants to start the traversal at the start key and
finish at the end key. If you're supplying descen
On Mon, May 5, 2014 at 11:19 PM, Nicolas Palacios wrote:
> Hi Jens, thanks for your comment.
>
> But if I try with:
> myview?startkey=["3566120224"]&endkey=["3566120224",{}]&descending=true
>
> I get this error:
>
> {"error":"query_parse_error","reason":"No rows can match your key
> range, reverse
Hi Jens, thanks for your comment.
But if I try with:
myview?startkey=["3566120224"]&endkey=["3566120224",{}]&descending=true
I get this error:
{"error":"query_parse_error","reason":"No rows can match your key
range, reverse your start_key and end_key or set descending=false"}
I'm lost. with
On May 5, 2014, at 11:53 AM, Nicolas Palacios wrote:
>myview?startkey=["3566120224"]&endkey=["3566120224",{}]&reversed=true
It’s “descending”, not “reversed”.
Docs are here: http://docs.couchdb.org/en/latest/api/ddoc/views.html
—Jens
Hi guys, thanks.
I'm testing some Couchdb features and I want get results with a reversed
order by insertion date, querying by "i" field
A sample doc:
{
"_id": "970c3a0fdbb23dde47fb4075091a4d2b",
"_rev": "1-54448147611ff5e89189bb44e58c1521",
"doc_type": "Test",
"e"
I've used blitz.io and really like it.
On May 5, 2014, at 8:24 AM, James Green wrote:
>>> now another too
On 2 May 2014 09:23, Alexander Shorin wrote:
> Hi Danilo,
>
> AFAIK JMeter has issues with handling requests workflow: when you need
> to make different requests in specific order, like (for couchdb) check
> document availability, create document, update it several times with
> different params a
I find it useful to include the type in the document id string. This way
you can always see which type of document you're dealing with. I have
made a little module, which helps in standardizing the id schema: docuri
[1].
You can also leave the type when deleting a document. Just put the
document wi
Hi,
I try to find a way to get deletes of documents with a specific type* from
the changes feed.
>From the documentation I don't see a way, neither with filters nor with
using a view as a filter, since both only get the current, deleted revision
where the type is already gone.
Also tried to get th
13 matches
Mail list logo
