Hi Matteo, On 10 Dec 2009, at 11:53, Matteo Caprari wrote:
> Interesting. > > Let's say I'd like to implement that feature. Where would you start? > Is there a document like "start hacking couchdb"? That's awesome! There are some docs on the wiki: http://wiki.apache.org/couchdb/Development They should do for an intro. If you get stuck, the #couchdb channel on irc.freenode.net is a good place to get help. You should also subscribe to the dev@ mailing list, if you haven't already, to discuss the direction of your patch. Please write if you have any more questions. Cheers Jan -- > > -teo > > On Thu, Dec 10, 2009 at 7:44 PM, Chris Anderson <jch...@apache.org> wrote: >> On Tue, Dec 8, 2009 at 1:11 PM, Matteo Caprari <matteo.capr...@gmail.com> >> wrote: >>> Hi Kosta. >>> >>> I'm trying to output an svg chart using a _list function, so no client >>> is consuming the view directly. >>> >>> I could find the max and scale the data inside the list, but that >>> would consume quite a lot of memory for big datasets, >>> unless it was possibe to reset the iterator... >>> >> >> There are a few use cases which could benefit from the ability to >> specify an array of view queries in the POST body. By querying the >> reduce, and then the non-reduce, you could do this in a list. But >> first we need that feature. It would look like a more generalized form >> of this: >> >> http://issues.apache.org/jira/browse/COUCHDB-523 >> >>> -teo >>> >>> On Tue, Dec 8, 2009 at 9:03 PM, <ko...@fillibach.de> wrote: >>>> Hi! >>>> >>>>> To scale the values I'need to know the maximum point, and I think >>>>> it'not possible to do that with map/reduce. >>>> >>>> You can find the maximum point using map/reduce. The division of all point >>>> must then be done manually given that point, e.g. in a view. Of course, >>>> doing it this way has problems with atomicity. >>>> >>>> HTH, >>>> Kosta >>>> >>>> >>>> >>> >>> >>> >>> -- >>> :Matteo Caprari >>> matteo.capr...@gmail.com >>> >> >> >> >> -- >> Chris Anderson >> http://jchrisa.net >> http://couch.io >> > > > > -- > :Matteo Caprari > matteo.capr...@gmail.com >
