Justin Pryzby writes:
> On Tue, Apr 20, 2021 at 09:07:52PM +0200, Erik Rijkers wrote:
>> I just happened to use the website-documentation and noticed that there the
>> change is not done: it still has the erroneous line, in the docs of 13
>> (current), and 12; the docs of 14devel are apparently
On Tue, Apr 20, 2021 at 09:07:52PM +0200, Erik Rijkers wrote:
> I just happened to use the website-documentation and noticed that there the
> change is not done: it still has the erroneous line, in the docs of 13
> (current), and 12; the docs of 14devel are apparently updated.
>
> That makes me
> On 2021.04.16. 10:00 Michael Paquier 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 @? operat
On Fri, Apr 16, 2021 at 11:00 AM Michael Paquier 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
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
> On 2021.04.03. 14:01 Erik Rijkers wrote:
>
> Hello,
>
> Attached is a small but confusing mistake in the json documentation (a @@
> instead of @?) that has been there since version 12. (It took me quite some
> time to figure that out while testing with the recent SQL/JSON patches --
> whi
