public inbox for [email protected]
help / color / mirror / Atom feedFrom: Marcos Pegoraro <[email protected]>
To: Tom Lane <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: pgsql-hackers <[email protected]>
Subject: Re: Missing jsonb_ ... functions on DOCs
Date: Mon, 11 May 2026 15:33:08 -0300
Message-ID: <CAB-JLwZLitbYDPa8zU5=tb+9t5eXA6Cq8qE5uSEbM9=x2ebVDQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAB-JLwbPuNY+4Ez48TZpXg-ZuxRSJ_igsNOa-nX7jBEs97qHCQ@mail.gmail.com>
<[email protected]>
<CAB-JLwb+m=gspBheMGWq9TCPqgD70K30AQ3bNxPzg3KBsym2Bg@mail.gmail.com>
<[email protected]>
Em seg., 11 de mai. de 2026 às 12:19, Tom Lane <[email protected]> escreveu:
> There are circa 800 entries in pg_operator (and that's just for the core
> code).
>
It is precisely because of this number of operators that I would like to
document the functions related to them.
When you read SQL and there is an operator, you need to think, "Did I use
the right operator? I'll check the documentation to see if that's the one."
If I use a word, I have no doubt. The word Diff is completely different
than the word Equal, but the operator != is very similar to the operator =
Maybe we can find a way to have both on DOCs.
Maybe put function name just after operator definition
jsonb @> jsonb → boolean (jsonb_contains())
Maybe a tooltip on that operator.
I don't know how, but from a user's point of view, I know that not
documenting isn't the best approach.
regards
Marcos
view thread (6+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Missing jsonb_ ... functions on DOCs
In-Reply-To: <CAB-JLwZLitbYDPa8zU5=tb+9t5eXA6Cq8qE5uSEbM9=x2ebVDQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox