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 jens@couchbase.com designates
 206.225.164.30 as permitted sender)
From: Jens Alfke <jens@couchbase.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Date: Thu, 9 Aug 2012 10:33:08 -0700
Subject: How does "local_seq" design doc option work?
Thread-Topic: How does "local_seq" design doc option work?
Thread-Index: Ac12VQj5xr3Ra7MpT9mMhEok9m9o7A==
Message-ID: <D893F7DB-69EA-4B10-A05B-8A46BBBD3E79@couchbase.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Could someone explain the "local_seq" design doc option? I've had a request=
 to implement it in TouchDB, but I don't know what it does. The only info a=
bout it I can find is the Jira issue COUCHDB-346*, which describes adding t=
hat property to the "options" object of a design doc, but it doesn't say wh=
at exactly it does. There's no link to a patch, either.

I've experimented by adding this option to a design doc in CouchDB 1.2, but=
 no matter how I query the view =97 like adding "?include_docs=3Dtrue&updat=
e_seq=3Dtrue&local_seq=3Dtrue" to the URL =97 I don't see sequence numbers =
appearing in the response.

As usual, I promise to add what I've learned to the CouchDB wiki. :)

=97Jens

* https://issues.apache.org/jira/browse/COUCHDB-346=