> On 22/11/2022 20:11 CET p...@cmicdo.com wrote:
>
> On Tuesday, November 22, 2022 at 01:16:02 PM EST, Peter J. Holzer
> wrote:
>
> > On 2022-11-22 17:39:04 +, Alastair McKinley wrote:
> > > > \copy footable from 'input.json' (format csv, escape '^B', delimieter
> '^C
> ', quote '^E')
> >
On Tuesday, November 22, 2022 at 01:16:02 PM EST, Peter J. Holzer
wrote:
> On 2022-11-22 17:39:04 +, Alastair McKinley wrote:
> > > \copy footable from 'input.json' (format csv, escape '^B', delimieter '^C
', quote '^E')
> > >
> > > where the control characters are the actual con
On 2022-11-22 17:39:04 +, Alastair McKinley wrote:
> > \copy footable from 'input.json' (format csv, escape '^B', delimieter '^C',
> > quote '^E')
> >
> > where the control characters are the actual control char, not the
> > caret-letter, and it requires no escaping escapes. I realize this
>
> From: p...@cmicdo.com
> Sent: 22 November 2022 15:30
> To: Alastair McKinley ;
> pgsql-general@lists.postgresql.org ; Erik
> Wienhold
> Subject: Re: copying json data and backslashes
>
> >
> > On Tuesday, November 22, 2022 at 10:16:1
>
> On Tuesday, November 22, 2022 at 10:16:11 AM EST, Erik Wienhold
wrote:
>
>
> > On 22/11/2022 15:23 CET Alastair McKinley
wrote:
> >
> > Hi all,
> >
> > I have come across this apparently common issue COPY-ing json and
wondering if
> > there is potentially a better solution.
>
> On 22/11/2022 15:23 CET Alastair McKinley
> wrote:
>
> Hi all,
>
> I have come across this apparently common issue COPY-ing json and wondering if
> there is potentially a better solution.
>
> I am copying data into a jsonb column originating from a 3rd party API. The
> data may have literal \r,
