Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 64771 invoked from network); 27 Jan 2011 11:14:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Jan 2011 11:14:28 -0000 Received: (qmail 55067 invoked by uid 500); 27 Jan 2011 11:14:26 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 54713 invoked by uid 500); 27 Jan 2011 11:14:23 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 54705 invoked by uid 99); 27 Jan 2011 11:14:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jan 2011 11:14:22 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of perfectly.normal.hacker@gmail.com designates 74.125.83.180 as permitted sender) Received: from [74.125.83.180] (HELO mail-pv0-f180.google.com) (74.125.83.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jan 2011 11:14:15 +0000 Received: by pvg7 with SMTP id 7so282233pvg.11 for ; Thu, 27 Jan 2011 03:13:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=WtQC/HVjVDa/c1M3G2q+/HkH6gvjoKHAVLe+4zlND5o=; b=KbGvvExhfGce1yCrnjgcDgENGAKJEs3Sabl+wVc3JXc6sQHe3R2LcR30xtVmbAx9rB ixNlyv+b2qabBBBpyVjOrdor9vKtdGEMys7G0nh5X1021kl40dsgwCyZb3vlRSQsPqhV FnL0byLhdQyDOCnh6h3PzF8Ob18asDqAgaDX0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=fRHnv4kXGwD1Ztcbgm80Mz7blhRc63fHRBEZAHBvjE/F8SO3GwK3hCnyIxxLtmQWW9 scnoGB6cT+3lWsjqbM9IeuplD2Jenh4R95UmyHrbMA92+n3iFQLR5iYCHaP8jzu/JgUO LO8lsC4mKlph0oTe2j9Pfhk6IQwiFLPOcIoI4= MIME-Version: 1.0 Received: by 10.142.240.4 with SMTP id n4mr1531006wfh.145.1296126833275; Thu, 27 Jan 2011 03:13:53 -0800 (PST) Received: by 10.142.128.12 with HTTP; Thu, 27 Jan 2011 03:13:53 -0800 (PST) Date: Thu, 27 Jan 2011 12:13:53 +0100 Message-ID: Subject: offset in view response From: Stefan Lang To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I couldn't find a single sentence about the offset member of a view response in either the reference on couchone.com or the reference on the wiki. Only thing I could find was this: "Note: If you use group_level, total_rows and offset will be omitted from the results (this is done to avoid scanning the entire tree. " here: http://wiki.apache.org/couchdb/HTTP_view_API Does it make sense to display this offset to the user in pagination (like "you are viewing elements 41 to 60 from 500")? And is it future-proof or only informal meta data? Or am I misunderstanding its meaning? Thanks, Stefan