Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of erich.oliphant@gmail.com
 designates 209.85.222.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=FeQ2lZPZdijVCOQ4pAbyQLWbryy8azdUR+gp1BMHWSu16DyRwp38AoJiKi2rBDNctv
         l24lkMVx5qG1mg2nF+5/O5ju7cY1BOwwyHMwPJn5q3jiAd/mDeSIDlh7dSIjq3u702dn
         tNvtQclJ1Cd0xMula08qe6fRArn/nn4IFQOCk=
MIME-Version: 1.0
In-Reply-To: <w2qe6101e101004280958q4875ca5tcb561d26af3e0bf4@mail.gmail.com>
References: <g2v49ba0cc11004271536x1b397f47h911dccb5c82726c@mail.gmail.com>
	 <x2he6101e101004271647zb51571f8i9da4fbda59cffd89@mail.gmail.com>
	 <21FA014E-CFEC-4B6E-A17F-9DFC9903F52B@gmail.com>
	 <w2qe6101e101004280958q4875ca5tcb561d26af3e0bf4@mail.gmail.com>
Date: Fri, 30 Apr 2010 16:39:06 -0400
Message-ID: <m2g49ba0cc11004301339qe1003d8czc0fb6a0439616d1e@mail.gmail.com>
Subject: Re: results without couch 'metadata'
From: erich oliphant <erich.oliphant@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=000e0cd112bc012e4604857a3cdf

--000e0cd112bc012e4604857a3cdf
Content-Type: text/plain; charset=ISO-8859-1

Ok, but do I have to regen JSON manually in this casem since the _list
function is designed to spit out arbitrary formats ?

On Wed, Apr 28, 2010 at 12:58 PM, Paul Bonser <misterpib@gmail.com> wrote:

> And of course, it didn't occur to me to mention that there was already
> an even more general solution already in place...
>
> On Tue, Apr 27, 2010 at 7:47 PM, Chris Anderson <jchris@gmail.com> wrote:
> > You can use a _list or _show function for this.
> >
> > Sent from my iPhone
> >
> > On Apr 27, 2010, at 4:47 PM, Paul Bonser <misterpib@gmail.com> wrote:
> >
> >> I'm pretty sure there is no such thing, but if it was to be added, I
> >> think it would be better to add something a little more general, such
> >> as "just_field" so you could do something like
> >> ?just_field=id/key/doc/value to get a list of all the
> >> ids/keys/docs/values, respectively.
> >>
> >> I don't like the name "just_field", that's just the first thing that
> >> came to mind, but I could see such a feature being useful.
> >>
> >> There'd be no need to wrap an extra doc around it, it could just be a
> >> json array returned, and it wouldn't make sense to strip out the _id
> >> and _rev, so with your example, you'd end up with the following being
> >> returned:
> >>
> >>   [
> >>   {"_id":"1","_rev":"1","important":"stuff"}
> >>   ]
> >>
> >> On Tue, Apr 27, 2010 at 5:36 PM, erich oliphant
> >> <erich.oliphant@gmail.com> wrote:
> >>>
> >>> Hi is there a way to get couch results without the extra metadata?
> >>>  Perhaps
> >>> instead of 'include_docs' where you get:
> >>>
> >>>
> >>>
> {"total_rows":1498,"offset":350,"rows":[{"id":"1","key":"1","doc":{"_id":"1","_rev":"1","important":"stuff"}}]}
> >>>
> >>> a 'docs_only' or something  option that would return something like
> >>> {[{"important","stuff"}]}
> >>>
> >>> --
> >>> Erich Oliphant
> >>>
> >>> "There are, in fact, two things, science and opinion, the former begets
> >>> knowledge, the latter ignorance"
> >>> -- Hippocrates of Cos
> >>>
> >>
> >>
> >>
> >> --
> >> Paul Bonser
> >> http://probablyprogramming.com
> >
>
>
>
> --
> Paul Bonser
> http://probablyprogramming.com
>


-- 
Erich Oliphant

"There are, in fact, two things, science and opinion, the former begets
knowledge, the latter ignorance"
-- Hippocrates of Cos

--000e0cd112bc012e4604857a3cdf--