Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1elFOO-0003LE-Cp for pgsql-docs@arkaria.postgresql.org; Mon, 12 Feb 2018 14:47:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1elFOM-00040q-BT for pgsql-docs@arkaria.postgresql.org; Mon, 12 Feb 2018 14:47:38 +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_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1elFOM-00040g-3V for pgsql-docs@lists.postgresql.org; Mon, 12 Feb 2018 14:47:38 +0000 Received: from mail-qt0-x242.google.com ([2607:f8b0:400d:c0d::242]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1elFOH-0000Oe-SY for pgsql-docs@lists.postgresql.org; Mon, 12 Feb 2018 14:47:37 +0000 Received: by mail-qt0-x242.google.com with SMTP id d8so19173818qtm.0 for ; Mon, 12 Feb 2018 06:47:33 -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=XonucI5bc7wH3qE+QijlKVPqu8IIhx5ba6eDDPeKvis=; b=rxRKGAygfQ1fAonl9JEUTwf0VSoQMD4dgvXFGOAhzAghjas/3u8yv2kBby0dpjBhvt PQbIy/ioOqhc7Zl/yuOaXhHKCPxG65b/b6ZuAMRywOo/6sq8otJQ+yXquNMq9o75a3eH aHlXoLvVKHmHGCeTnoF2Dzwdve7YSHK7oQD2Hl6bXnD6QiO1guNsFj712VZwc6bjUt2J tv1Dkx80EA2dPJt2XCTvTePyqvss9EyJMQX9mnInXs8LoGfxOpvn11MHBbxlBKofAKQF HdVq8Mp5pN4BWJvL2TAlApkethKk3GO9WuZz5/tgxClv3icVx+zDlShC+UkLqTj2mKr5 kEWw== 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=XonucI5bc7wH3qE+QijlKVPqu8IIhx5ba6eDDPeKvis=; b=ZIaFEcgZFcgZeUhXTt3B8WGSIRgUpR+gVipKshzFY1J7YBOTVkEECfH0xwqDX0mQxr 3nOOm2GHHI5vSp3YhR6ZJOU3lXBcQREliGTNq2AhCYw1zIuphKGMAs+wUmdgITCHjhZL lqTevP2A//Clgm2rs+1+RXHnxiiZPJHT/+TBKlZQwzxp7OZeQMGWrf8BQzErhiNOoybw 2BBTBGN5rT46iXv9+kg/5YLnHSwW+bGl8phyFdTuOSPOhuBW4/OKLOpkJ+LJyQfJnewF bQxwczSFjef1/b+ohd9QJM7gF5haQfkm81ko20gVA40pMISjzcd5NHr9IR3O/YwGoNyy GIFA== X-Gm-Message-State: APf1xPB4XlDrr1OpFaTFcmbvv7ondfyYOizP4mIAz8pT/gen6k1bHlZR SEpSKYwJQzKgLfnd4nRLrS6XKgX7rC8u5swTwQI= X-Google-Smtp-Source: AH8x226r2i7Df7U6oR7XA3689+Ck7HXFm82xYL88KyP0m6/qMTlQls8Zq4pby/c85COE8+SwxQgVkVZdCMctT4cLR6A= X-Received: by 10.237.37.6 with SMTP id v6mr18536003qtc.124.1518446852041; Mon, 12 Feb 2018 06:47:32 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.182.35 with HTTP; Mon, 12 Feb 2018 06:47:31 -0800 (PST) In-Reply-To: <151844411228.1459.13397476712825545135@wrigleys.postgresql.org> References: <151844411228.1459.13397476712825545135@wrigleys.postgresql.org> From: "David G. Johnston" Date: Mon, 12 Feb 2018 07:47:31 -0700 Message-ID: Subject: Re: complex documentation and hard to find the reference To: saikiran.rachakonda@vasudhaika.net, pgsql-docs@lists.postgresql.org Content-Type: multipart/alternative; boundary="001a1142c84039f196056504f5dc" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --001a1142c84039f196056504f5dc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Feb 12, 2018 at 7:01 AM, PG Doc comments form < noreply@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.5/static/functions-json.html > Description: > > with the prior experience of mysql or mongoDb or any other. Documentation > can be understood. But without any experience of those, hard to try the > JSONB data type. > > =E2=80=8BThe functions chapter assumes that one has read the earlier "Data = Types" chapter for JSON first. There are many examples there. https://www.postgresql.org/docs/10/static/datatype-json.html > Specify operand places in a select query (give the entire example query). > =E2=80=8B =E2=80=8BThat would be unnecessarily verbose in almost all cases. Is there= a specific one that is particularly confusing for which a more detailed example should provided? The function reference chapter assumes that people know how to write queries and just need to know which functions are available. Other chapters in the documentation cover describing how to do the former.=E2=80= =8B =E2=80=8BDavid J. =E2=80=8B --001a1142c84039f196056504f5dc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Fe= b 12, 2018 at 7:01 AM, PG Doc comments form <noreply@postgresql.org> wrote:
The following documentation comment has been logged on the website:=

Page: https://www.postgresql.org/= docs/9.5/static/functions-json.html
Description:

with the prior experience of mysql or mongoDb or any other. Documentation can be understood. But without any experience of those, hard to try the
JSONB data type.


=E2=80=8BThe functions chapter assu= mes that one has read the earlier "Data Types" chapter for JSON f= irst.=C2=A0 There are many examples there.
=
= https://www.postgresql.org/docs/10/static/datatype-json.html
=
=C2=A0
Specify operand places in a select query (give the entire example query).
=E2=80=8B
=E2=80=8BThat would be unnecessarily verbose in almost all cases= .=C2=A0 Is there a specific one that is particularly confusing for which a = more detailed example should provided?

The function re= ference chapter assumes that people know how to write queries and just need= to know which functions are available.=C2=A0 Other chapters in the documen= tation cover describing how to do the former.=E2=80=8B

=E2=80=8BDavid J.=
=E2=80=8B

--001a1142c84039f196056504f5dc--