| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | reader 1001 <007reader(at)gmail(dot)com> |
| Cc: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Abnormal JSON query performance |
| Date: | 2018-05-16 03:59:25 |
| Message-ID: | CAKFQuwapkgj6X9Yv3UH=jaS5uvHCvmcw2RR8e_LWbQ3M3QY_Fw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tuesday, May 15, 2018, reader 1001 <007reader(at)gmail(dot)com> wrote:
> Yes, I realized it by now, thank you.
> My question remains for hierarchical keys in a JSON document. If I have a
> document like below, I clearly can extract key1 using the described rowtype
> definition. How can I specify selected keys deeper in the document, e.g.
> key3 and key5?
> {
> key1:value1,
> key2: {
> key3:value3},
> key4:[
> {
> key5:value5
> },
> {
> key6:value6
> }
> ]
> }
>
>
I believe you would need a type for each subtree and apply the function
multiple times with the result of one feeding the next.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Dolgov | 2018-05-16 07:12:19 | Re: Abnormal JSON query performance |
| Previous Message | reader 1001 | 2018-05-16 03:42:16 | Re: Abnormal JSON query performance |