From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, "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 14:25:18 |
Message-ID: | CAPpHfdtmMJv9RH3BYivxh7yXoHtz1cADxrusWWwAm46u11-5Xg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-docs pgsql-hackers |
On Fri, Apr 16, 2021 at 11:00 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> 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.
My apologies for missing this. And thank you for taking care!
------
Regards,
Alexander Korotkov
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-04-16 15:30:34 | pgsql: Fix wrong units in two ExplainPropertyFloat calls. |
Previous Message | Laurenz Albe | 2021-04-16 14:09:12 | Re: pgsql: SQL-standard function body |
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2021-04-19 08:00:07 | Rounding strategy |
Previous Message | Michael Paquier | 2021-04-16 08:00:27 | Re: fix old confusing JSON example |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-04-16 14:29:35 | Re: Error when defining a set returning function |
Previous Message | Tom Lane | 2021-04-16 14:03:42 | Re: Bogus collation version recording in recordMultipleDependencies |