Re: SQL/JSON path issues/questions

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Liudmila Mantrova <l(dot)mantrova(at)postgrespro(dot)ru>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Thom Brown <thom(at)linux(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SQL/JSON path issues/questions
Date: 2019-07-07 21:30:01
Message-ID: CAPpHfduym92tpfbSCTLiS8USvjaCyXLKvL6z7cEidr+GL=wLZw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 4, 2019 at 4:38 PM Liudmila Mantrova
<l(dot)mantrova(at)postgrespro(dot)ru> wrote:
> Thank you!
>
> I think we can make this sentence even shorter, the fix is attached:
>
> "To refer to a JSON element stored at a lower nesting level, add one or
> more accessor operators after <literal>@</literal>."

Thanks, looks good to me. Attached revision of patch contains commit
message. I'm going to commit this on no objections.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Attachment Content-Type Size
0004-clarify-jsonpath-docs-5.patch application/octet-stream 10.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-07-07 21:51:04 Re: Avoiding deadlock errors in CREATE INDEX CONCURRENTLY
Previous Message Tomas Vondra 2019-07-07 21:02:05 Re: [PATCH] Incremental sort (was: PoC: Partial sort)