On Jul 21, 2011, at 7:01 AM, Kevin R. Coombes wrote:
And I would therefore argue in favor of deprecation. In the long run,
it is better to teach people to use "group_level=exact" than to
repeatedly have to explain this issue to them. I think it's a bad idea
to promote behavior (using "group=tru
On Thu, Jul 21, 2011 at 7:42 AM, Vivek Pathak wrote:
> This would make it hard to edit the html in a normal editor. Now I can
> keep my (templatized) html intact in a file, and upload it to a place it
> couchdb.
>
I take this to mean that you use some sort of editor with a WYSIWYG
interface. Si
To this user, it still smells like a bug
And I would therefore argue in favor of deprecation. In the long run,
it is better to teach people to use "group_level=exact" than to
repeatedly have to explain this issue to them. I think it's a bad idea
to promote behavior (using "group=true") t
I tried using require, but from what I could gather through trial and
error, I would need to wrap the html in a js wrapper like this:
var exports.html = ' ... html code ' ;
This would make it hard to edit the html in a normal editor. Now I can
keep my (templatized) html intact in a file,
I was going to suggest making a module that had all your static data in it
and just require it in to use. Added benefit of being able to use it in
other design doc functions that support CommonJS modules and also using it
in node.js if you ever needed to.
Sounds like you are doing something simila
Rather than deprecate, I'd convert it to a 400 bad request (or leave
as is). Specifying two different values for the same parameter sounds
unambiguously 'bad' to me. The fact that it's non obvious to the user
that they are doing so is further motivation to improve the
information in the response.
Hi Benoit,
I'm working on a project like LinkedSensorData and I'm using CouchDB as
backend and Python as web frontend and in distributed data acquisition
devices.
Since I can't go to CCC, please keep me updated.
Thanks!
Fabio Di Bernardini (Italy)
Il 18/07/2011 12:16, Benoit Chesneau ha sc
Hey Max,
Thanks for sending the links! However I don't find the solution for my
problem in skip, considering they are inexpensive for large data sets, which
is the case with my view.
I was wondering if I can attach a pagination widget to my _attachments?
I haven't got to the point to use url rew
Max Ogden wrote:
> you can also do pagination using just skip:
> https://github.com/maxogden/recline/blob/master/attachments/script/recline.js#L105(demo:
> http://max.couchone.com/senators/_design/recline/_rewrite)
I never tried it, but learned from the mailinglist that using skip for
pagination
h there
to do startkey_docid you have to specify both startkey and startkey_docid.
here's an example working query
http://monocl.es/api/stream?descending=true&limit=20&startkey=%222011-07-19T04%3A24%3A43.466Z%22&startkey_docid=%160c79004a9821c0414e69ad01b330%22&skip=1(demo:
http://monocl.e
Hello,
I'm a newbie to couchdb v1.1.0. I have been struggling with implementation
of pagination in couchdb. I have been through the guide and wiki pages to
understand the concept of startkey and startkey_docid to implement
pagination however I am unable to understand the implementation part. Do I
11 matches
Mail list logo
