From user-return-22886-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Tue Nov 20 08:28:14 2012 Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD75FEBFB for ; Tue, 20 Nov 2012 08:28:14 +0000 (UTC) Received: (qmail 95401 invoked by uid 500); 20 Nov 2012 08:28:14 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 94236 invoked by uid 500); 20 Nov 2012 08:28:11 -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 94196 invoked by uid 99); 20 Nov 2012 08:28:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Nov 2012 08:28:09 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of cliffano@gmail.com designates 209.85.212.52 as permitted sender) Received: from [209.85.212.52] (HELO mail-vb0-f52.google.com) (209.85.212.52) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Nov 2012 08:28:02 +0000 Received: by mail-vb0-f52.google.com with SMTP id ez10so3040284vbb.11 for ; Tue, 20 Nov 2012 00:27:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=nE4t2a9IVhH5OQz1drXG0wzA4/5VZGOujMUz5lqChxc=; b=cX2OftKIVo2DH3gU73sb0GGBXkf0CcfrPAnsLHN1JvR00fuKQ4zWYoMp4CcAUAvVIg fuzD6lM49AlqnEelYFOlVG6rWvhCYGeQ/i63EN8L+/X7a+kgGHu62Nc2MEXI5LyWzxsq UZSp7aF6OJ6nd92M9tsaeipxBIc1Fx4c5SA6GCpUB+9Ze18/G7Tt38n8XMt2cjED/Fy7 xL1erE96fwvsu3k/JfuPhpzW3nWwEcHTY5fSYLBGkTQ6y3q1C1B55CCOBnPpUJTvS1CO yn3vdK2HVaHHcj+V+hGaJD+19xZNNTYii9qRQnHHiYJx82ZPCP6ei2lFXio1u8kRXRvX qlMg== MIME-Version: 1.0 Received: by 10.58.221.130 with SMTP id qe2mr21196818vec.14.1353400061207; Tue, 20 Nov 2012 00:27:41 -0800 (PST) Received: by 10.58.239.3 with HTTP; Tue, 20 Nov 2012 00:27:41 -0800 (PST) Date: Tue, 20 Nov 2012 19:27:41 +1100 Message-ID: Subject: deleted database while longpolling _changes From: Cliffano Subagio To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=047d7bf0cabee3237f04cee90161 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bf0cabee3237f04cee90161 Content-Type: text/plain; charset=ISO-8859-1 Hi, I have a database which _changes notification is being longpolled. I notice that when I delete this database, the response body will have results containing an empty array, along with a last_seq property, and status code 200. Can the empty results array be used to identify that the database was deleted? Is there any other events that might result in an empty results array? Another thing I'm curious about is the last_seq property value. I created a new database, query dbname/_changes, it return last_seq 0 as expected {"results":[ ], "last_seq":0} But when I query dbname/_changes?heartbeat=1000&feed=longpoll&since=123 I get the since parameter value as last_seq property value, like this {"results":[ ... ], "last_seq":123} What is the reasoning behind returning since parameter value 123 instead of the real last_seq 0? Just by checking the response body, how to determine whether last_seq 123 is really the number of changes in the database? or if 123 is only since parameter value? Cheers, Cliff. --047d7bf0cabee3237f04cee90161--