Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: <1B96FDDF-E05C-4A3A-B2C7-FFC03BA581CF@couchbase.com>
References: <1B96FDDF-E05C-4A3A-B2C7-FFC03BA581CF@couchbase.com>
Date: Tue, 15 Jan 2013 12:48:34 -0500
Message-ID: 
 <CABvT1DEGDCJyvEuFsNJZbXi_NJwJna8NHDnQvpr2h532s0V18g@mail.gmail.com>
Subject: Re: Did BigCouch recently change sequence IDs to be arrays?
From: Robert Newson <rnewson@apache.org>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Yes, that's true. An update_seq is always valid JSON and should be
treated opaquely, though a change does flush out bugs in client
libraries and such.

B.

On 15 January 2013 12:32, Jens Alfke <jens@couchbase.com> wrote:
> I just got a bug report about TouchDB failing to sync with BigCouch. From=
 the symptoms, it appears that BigCouch has recently changed its sequence I=
Ds (as returned from _changes) from strings to arrays. Is that true?
>
> I don=92t have a local BigCouch to test against currently, but I just con=
firmed that Cloudant is still using strings for sequence IDs; they look lik=
e this:
>> "last_seq":"5865-g1AAAADzeJzLYWBgYMlgTmFQSElKzi9KdUhJMtbLTS3KLElMT9VLzsk=
vTUnMK9HLSy3JAapkSmRIsv___39WEgMD61ZUbeZ4tCU5AMmkepjOw6g6TfDozGMBkgwNQAqoeT=
9Y913i7YXoPgDRDbF7ShYAyj1QSA=94
>
> If BigCouch is now using arrays, then I need to fix my code to serialize =
them properly in the =93?since=94 parameter to the _changes feed URL. But t=
his is a bit confusing =97 if I JSON-encode the sequence ID, then IDs that =
are strings will now have double-quotes around them, and I don=92t know if =
Cloudant will understand that. Do I need to special-case based on the type,=
 i.e. stripping the quotes if it=92s a string?
>
> =97Jens