Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSM2q-0001Qh-SO for pgsql-docs@arkaria.postgresql.org; Wed, 06 Nov 2019 14:12:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iSM2p-0005IC-4B for pgsql-docs@arkaria.postgresql.org; Wed, 06 Nov 2019 14:12:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSM2o-0005I5-QT for pgsql-docs@lists.postgresql.org; Wed, 06 Nov 2019 14:12:22 +0000 Received: from mail-qt1-x82d.google.com ([2607:f8b0:4864:20::82d]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iSM2l-0005K8-Sl for pgsql-docs@lists.postgresql.org; Wed, 06 Nov 2019 14:12:22 +0000 Received: by mail-qt1-x82d.google.com with SMTP id o11so28763644qtr.11 for ; Wed, 06 Nov 2019 06:12:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=ApLZRR1DWrfQiylORlw5kalgMFmxBU+c5qf8OcSMI6A=; b=ZsLz9BLfgUWJ8YBkKk8n1RFivPOuRc3RBW2Dj5lySTewXlyp7Wr4A0EWzXBGZgPEb9 x4cFQddCTPSRMZj39Y6qe7uzk4JINWhL4TP31PXMNfQfhFYd8YWu8+goxC631MmNBeZ3 I+uWFMzXjT4w+c1wscWp5ENzobT2zUELn0QJdn7IB2ytI72RTdTRedayXwDlt4GxpWnK SmHhXFbQq6hvi0Ag8ECjNIWq1JCmBbpRN3XEXxWC51reagGLXyOknmObk3qq6jh3v8f4 k73DDqFELh0nlVuSpdReZFyDvQjtSJLPysVGqN8AKIK8kPUSif0uSrGRuuznSPjDsnkL 7H/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=ApLZRR1DWrfQiylORlw5kalgMFmxBU+c5qf8OcSMI6A=; b=AIj84zdqoDm4TaI1ZTHRnHAzGxPDkE06hxZn9PiV60EkqPdgIDYIlaH1xXkKHbJqGY 9pk+F2evApTPlY2kpXfvNW6MXWBpEgQ3r4nm5hCB9nC8DQsRgysvvPSIF4sG4bmw7vrV JCyd5JlS0YV/k9hss39b9BjZEwygvdamtiv1xTRbp+g0p5YNQzJpexqiRf+w6HUFkHLz awSEg6egdEP+08vkenLmCzpp17PnmWInX3iwlvZUcLEP/OT4s7ifSpvqDjmfXWMDFYue lPwL+ukdciqmfCqHqZZGRnH/EVGdyyHDU52/Bgd8W8XTEhQarOak2GqjZMlOyeGGcIra Gi4g== X-Gm-Message-State: APjAAAUQvM+yUz4EZ2axwE4Rtx60T8x58GehBNl/JyxtaoEQDPFKQ4vq x7pBPQi9Wky9E09kP5elB9Z1LY7Ohr3hwrTlaFjyTw== X-Google-Smtp-Source: APXvYqzyH73J+MjLcdJUlvziTyyAq36ane6KkTYWYi4JgQZEufqOLR04bXqWfLGua1hnt9xSMXV9B3jECI5KwxesxUE= X-Received: by 2002:ac8:5396:: with SMTP id x22mr2596447qtp.225.1573049537902; Wed, 06 Nov 2019 06:12:17 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a0c:ca05:0:0:0:0:0 with HTTP; Wed, 6 Nov 2019 06:12:17 -0800 (PST) In-Reply-To: <157301068439.14260.3440469821975939421@wrigleys.postgresql.org> References: <157301068439.14260.3440469821975939421@wrigleys.postgresql.org> From: "David G. Johnston" Date: Wed, 6 Nov 2019 07:12:17 -0700 Message-ID: Subject: Re: Adding a Column documentation is misleading To: "gavinflower@archidevsys.co.nz" , "pgsql-docs@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000ebba930596ae2286" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000ebba930596ae2286 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tuesday, November 5, 2019, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/12/ddl-alter.html > Description: > > In 5.6.1. Adding a Column, there is a kind of example 'ALTER TABLE produc= ts > ADD COLUMN description text;' > > The words 'description' and 'text' are misleading -- as according to the > formal documentation of the SQL command > (https://www.postgresql.org/docs/12/sql-altertable.html), they should be > 'column_name' and 'data_type'. > > A similar problem exists for removing a column, and other actions. > Chapter 5 is tutorial-like and uses actual meaningful names instead of syntax placeholders. I don=E2=80=99t really see a problem aside from maybe= a different example name could be chosen. Making it column_name isn=E2=80=99= t an improvement. David J. --000000000000ebba930596ae2286 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tuesday, November 5, 2019, PG Doc comments form <noreply@postgresql.org> wrote:
The following documentation comment has been logged on t= he website:

Page: https://www.postgresql.org/docs/12/ddl-alter.html
Description:

In 5.6.1. Adding a Column, there is a kind of example 'ALTER TABLE prod= ucts
ADD COLUMN description text;'

The words 'description' and 'text' are misleading -- as acc= ording to the
formal documentation of the SQL command
(https://www.postgresql.org/docs/12/sql-altertable.html= ), they should be
'column_name' and 'data_type'.

A similar problem exists for removing a column, and other actions.

Chapter 5 is tutorial-like and uses actual= meaningful names instead of syntax placeholders.=C2=A0 I don=E2=80=99t rea= lly see a problem aside from maybe a different example name could be chosen= .=C2=A0 Making it column_name isn=E2=80=99t an improvement.

<= /div>
David J.=C2=A0
--000000000000ebba930596ae2286--