Re: fix old confusing JSON example
От | Erik Rijkers |
---|---|
Тема | Re: fix old confusing JSON example |
Дата | |
Msg-id | 1262514661.622692.1618945673016@webmailclassic.xs4all.nl обсуждение исходный текст |
Ответ на | Re: fix old confusing JSON example (Michael Paquier <michael@paquier.xyz>) |
Список | pgsql-hackers |
> On 2021.04.16. 10:00 Michael Paquier <michael@paquier.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. Great, thank you. I just happened to use the website-documentation and noticed that there the change is not done: it still has the erroneousline, in the docs of 13 (current), and 12; the docs of 14devel are apparently updated. That makes me wonder: is there a regular html-docs-update (dayly? weekly?) of doc-bugs of this kind in the website-docs ofcurrent and earlier releases? To be clear, I am talking about the lines below: 'GIN index supports @@ and @? operators' on pages https://www.postgresql.org/docs/13/datatype-json.html https://www.postgresql.org/docs/12/datatype-json.html where the change that was pushed was to correct the second example from @@ to @? thanks, Erik Rijkers > > My apologies for the delay. > -- > Michael
В списке pgsql-hackers по дате отправления: