Re: fix old confusing JSON example

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Erik Rijkers <er(at)xs4all(dot)nl>
Cc: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: fix old confusing JSON example
Date: 2021-04-16 08:00:27
Message-ID: YHlEG1Ns6RKrqKpQ@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-docs pgsql-hackers

On Sat, Apr 03, 2021 at 02:28:38PM +0200, Erik Rijkers wrote:
> So, that gives information on two operators, and then gives one
> example query for each. Clearly, the second example was meant to
> illustrate a where-clause with the @? operator.
>
> Small change to prevent great confusion (I'll admit it took me far
> too long to understand this).

Once one guesses the definition of the table to use with the sample
data at disposal in the docs, it is easy to see that both queries
should return the same result, but the second one misses the shot and
is corrected as you say. So, applied.

My apologies for the delay.
--
Michael

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2021-04-16 09:06:37 pgsql: psql: Small fixes for better translatability
Previous Message Michael Paquier 2021-04-16 07:57:49 pgsql: doc: Fix typo in example query of SQL/JSON

Browse pgsql-docs by date

  From Date Subject
Next Message Alexander Korotkov 2021-04-16 14:25:18 Re: fix old confusing JSON example
Previous Message Michael Paquier 2021-04-16 06:35:32 Re: Typo in DATATYPE-JSONPATH

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2021-04-16 08:30:58 Re: Converting built-in SQL functions to new style
Previous Message Noah Misch 2021-04-16 07:56:55 Re: Allowing to create LEAKPROOF functions to non-superuser