From dev-return-49196-archive-asf-public=cust-asf.ponee.io@couchdb.apache.org Thu Mar 26 07:12:10 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 57B2C180637 for ; Thu, 26 Mar 2020 08:12:10 +0100 (CET) Received: (qmail 87278 invoked by uid 500); 26 Mar 2020 07:12:09 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 87266 invoked by uid 99); 26 Mar 2020 07:12:09 -0000 Received: from Unknown (HELO mailrelay1-lw-us.apache.org) (10.10.3.159) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Mar 2020 07:12:09 +0000 Received: from mail-lj1-f171.google.com (mail-lj1-f171.google.com [209.85.208.171]) by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id A583DF8B for ; Thu, 26 Mar 2020 07:12:08 +0000 (UTC) Received: by mail-lj1-f171.google.com with SMTP id t17so5247627ljc.12 for ; Thu, 26 Mar 2020 00:12:08 -0700 (PDT) X-Gm-Message-State: ANhLgQ1dL3MV0NFLVmimLvCKPo2o4nLBLOrhe8uzf98XjaOJsIJvIHW8 fBypb9Dwaect1NO62FoIJvnFB4qSvkHA7hX3c1cjwA== X-Google-Smtp-Source: APiQypKnJOItDVoLtu/swTsgLCvw1aJKI9vUKRfMPNra7dbSCE/SQVytqQZlS9GZLVGULDAP7ijuX80oHnZI3YxtA3Y= X-Received: by 2002:a2e:86ca:: with SMTP id n10mr4075644ljj.219.1585206727695; Thu, 26 Mar 2020 00:12:07 -0700 (PDT) MIME-Version: 1.0 From: Garren Smith Date: Thu, 26 Mar 2020 09:11:56 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: _all_docs collation To: CouchDB Developers Content-Type: multipart/alternative; boundary="000000000000e6a13805a1bcb378" --000000000000e6a13805a1bcb378 Content-Type: text/plain; charset="UTF-8" Hi Everyone, While working on the Mango implementation for FDB, I've noticed that _all_docs has some weird ordering collation. If you do something like GET /db/_all_docs?startkey={} it will return all the documents even though in view collation an object is ordered after strings. The reason I've noticed this is that in the pouchdb-find tests we have a few tests that check that {selector: {_id: {$gt: {}}} return all the docs in the database [0]. This ordering feels wrong to me, but I'm guessing its been around for a while. Currently for _all_docs on FDB, we have it that if you did the above startkey query, it would not return any documents as we are following the view collation ordering. I want to know whether we should keep the old _all_docs ordering or rather standardize on view collation ordering everywhere? I would prefer we change it, but I'm not sure the implications of that for client libraries and users. Changing it would be a breaking change, but since 4.0 is going to be a lot of breaking change I think this would be our best chance to do this. Cheers Garren [0] https://github.com/nolanlawson/pouchdb-find/commit/e1ca2e2d18041f05a3d19bce4254f4d7b349ad20 --000000000000e6a13805a1bcb378--