| From: | Shaozhong SHI <shishaozhong(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Rob Sargent <robjsargent(at)gmail(dot)com>, pgsql-sql <pgsql-sql(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Turn a json column into a table |
| Date: | 2022-02-20 03:31:22 |
| Message-ID: | CA+i5Jwbfdn4Ai+dX2KtgUmYAZwWOH_n+=V9X9_Lhh_vONraeZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Sunday, 20 February 2022, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Sat, Feb 19, 2022 at 5:58 PM Shaozhong SHI <shishaozhong(at)gmail(dot)com>
> wrote:
>
>> It is impossible to produce any self-contained example.
>>
>
> We are talking about a data table and pure SQL, it is not impossible to
> produce a self-contained example. Even if said example fails to produce
> the desired behavior.
>
> Another approach is to run psql and capture everything to a text file and
> share that - so even without the reproducer we can see exactly what you are
> seeing.
>
> David J.
> That did not work at all. I was given data sets to examine. These got
> loaded with ogr2ogr. But very strange behavior occur as I described in
> Posters.
>
Made copy back to disk. The key and value mentioned disappeared.
Regards, David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2022-02-20 09:07:28 | Aw: Re: Turn a json column into a table |
| Previous Message | David G. Johnston | 2022-02-20 01:08:27 | Re: Turn a json column into a table |