Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
    boundary="----_=_NextPart_001_01CB0C32.3345879D"
Subject: Can I get just the keys from a view? [SEC=UNCLASSIFIED]
Date: Tue, 15 Jun 2010 11:56:45 +0930
Message-ID: 
 <DB2FF420856DB942829BF029A7E3C19601FFA57E@ednex514.dsto.defence.gov.au>
Thread-Topic: Can I get just the keys from a view? [SEC=UNCLASSIFIED]
Thread-Index: AcsMMjL0AE6ApUAOSHu4IeBLcwE6rw==
From: "Lowry, Matthew" <Matthew.Lowry@dsto.defence.gov.au>
To: <user@couchdb.apache.org>

------_=_NextPart_001_01CB0C32.3345879D
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi folks. A Couch newbie here with a question regarding the view API.=0D=0A=
 =0D=0AIs there any way that I can query a view and get just the key for eac=
h=0D=0Arow, and omit the value?=0D=0A =0D=0AThe reason I ask is I'm working =
with a view that generates a massive=0D=0Aamount of data - each document in =
the database generates many hundreds=0D=0Aof rows in the view. Each row has =
a large value object. But all I want=0D=0Ato do is get the keys. So it's was=
ting a massive amount of time and=0D=0Aresources, both client and server sid=
e, to have to pull both the key and=0D=0Avalue object for every row in the v=
iew when all I want to see is the=0D=0Akey.=0D=0A =0D=0ASo is there actually=
 a mechanism in the view API to pull just the key=0D=0Afrom each row of a vi=
ew? And if not, why not? That would be curiously=0D=0Aasymmetrical with the =
document API, which allows me to get the IDs of=0D=0Aall the documents witho=
ut requesting the documents themselves.=0D=0A =0D=0ACheers.=0D=0A=0D=0AIMPOR=
TANT: This email remains the property of the Department of Defence and is su=
bject to the jurisdiction of section 70 of the Crimes Act 1914. If you have =
received this email in error, you are requested to contact the sender and de=
lete the email.=0D=0A
------_=_NextPart_001_01CB0C32.3345879D--