Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbWhh-00067W-Uq for pgsql-docs@arkaria.postgresql.org; Wed, 20 May 2020 21:56:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jbWhf-0002T4-Lk for pgsql-docs@arkaria.postgresql.org; Wed, 20 May 2020 21:56:43 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbWhf-0002Sx-Cu for pgsql-docs@lists.postgresql.org; Wed, 20 May 2020 21:56:43 +0000 Received: from mail-ot1-x344.google.com ([2607:f8b0:4864:20::344]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jbWhc-0001Sw-Qv for pgsql-docs@lists.postgresql.org; Wed, 20 May 2020 21:56:43 +0000 Received: by mail-ot1-x344.google.com with SMTP id 63so3815730oto.8 for ; Wed, 20 May 2020 14:56:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=FmDoKcbrMD5AESvITP8oBHzEUkAerhObrY241efLbEY=; b=g2EvfLK+3IYIPT5L+2CSwa35yYsHrBv/FfbLnbpVAEW4QffksMkscdih/wu6XCeU9q dvbGyxaYcRFuErvN+P6pdbLZJksfQEGHS8X2r+WAyokrxdfMglKSfsQ5LjXVPuGgiD68 Jlu5+AxoaW0fldBnP7HiAkiJxwfDonT11F9aOW786CsOgbmDHsV64YYPr7AtMelNDbRl YdHCo8NYc3i8afJXYhqa0Whwi3/z0euH26Su+mJ/L0OaijH5NcVf598kQiOfPBgAkpR0 hwcLYKxcIBJodCvpRiGllwiU3eLEkk1V7eTXVWoQ+1/vgCPQnIXlhD8dpySL7oXl4jZv aqcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=FmDoKcbrMD5AESvITP8oBHzEUkAerhObrY241efLbEY=; b=i0iO+5iadR2vMr6pyWCySMGQ4ECvPYgxfZe3m2Xgeor8JsUnm5F4EwwmAFOlVlL37N TUeHYS6XEYLIvzfkSwNYkStEaXXDUdM7la6QqqOG/AeW+W55eWT44JN71WqDb1Mq4GF+ WIpVbms2+kN2Hgmicy5lR/J6iyqoLN71eWYgUYVnbJnVE00q1yjIiAfZwF/DxE9wqLYE QVxCSvv7HPIh8DbUjRbRzlJCvYMKclKZb+s/nO7wSjqu57VOm7oh17BuXk1bY09bgc6a njC8Sg9SPEebHAi8QdeIlUqAhE13vsXlHlj5YuC5d5M3tvLKrd2Qv4M9EtnkKSahYodc UxwQ== X-Gm-Message-State: AOAM530qBxoZtzXWY6i0x/kcC/SNmvwwHTkEgFsyh5xZYqF0a6wXQwP9 qIaP6vPRxRXVV8w0W09RfpnZVlrhgfGDWHjMuj0= X-Google-Smtp-Source: ABdhPJwlgbSlQGnzTcY0kR5wQNRDUXDE8fphWjPP9v1N5PePdWqFikFCFEQU1cX/OzfazxXeYGj/iNfEOEG0xV40IGc= X-Received: by 2002:a05:6830:1e32:: with SMTP id t18mr5003894otr.185.1590011798839; Wed, 20 May 2020 14:56:38 -0700 (PDT) MIME-Version: 1.0 References: <158996922318.7035.10603922579567326239@wrigleys.postgresql.org> In-Reply-To: <158996922318.7035.10603922579567326239@wrigleys.postgresql.org> From: Thomas Munro Date: Thu, 21 May 2020 09:56:02 +1200 Message-ID: Subject: Re: Change JOIN tutorial to focus more on explicit joins To: shammat@gmx.net, pgsql-docs@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, May 21, 2020 at 1:37 AM PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/tutorial-join.html > Description: > > The tutorial about joins makes the following statement about the explicit > JOIN operator: > > > This syntax is not as commonly used as the one above > > I think in 2020 this claim is no longer true, and I would love to see the > manual prefer the "modern" explicit JOIN operator rather than sticking to > the ancient implicit joins in the WHERE clause. +1 The "new" syntax is 28 years old, from SQL 92. I don't see too many SQL 86 joins. Would you like to write a documentation patch?