Re: New "single" COPY format - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: New "single" COPY format
Date
Msg-id CAJ7c6TPsLXoJQ4rMh7C+onESCzutWtBVe0dOff3t7k8YhzDvfg@mail.gmail.com
Whole thread Raw
In response to Re: New "single" COPY format  (Aleksander Alekseev <aleksander@timescale.com>)
List pgsql-hackers
Hi,

> > Recap: This is about adding support to import/export text-based formats such as
> > JSONL, or any unstructured text file, where wanting to import each line "as is"
> > into a single column, or wanting to export a single column to a text file.
>
> Sorry for being late for the discussion.
>
> I disagree with the idea of adding a new format name for this. Mostly
> because it is *not* a new format and pretending that it is will be
> just a poor and/or confusing user interface.
>
> IMO it should be 'text' we already have with special options e.g.
> DELIMITER AS NULL ESCAPE AS NULL. If there are no escape characters
> and column delimiters (and no NULLs designations, and what else I
> forgot) then your text file just contains one tuple per line.

Personally I wouldn't mind a special syntax such as LINES AS IS or
maybe COPY AS IS for convenience. Perhaps we should discuss it
separately though as a syntax sugar for a long list of options we
already support.

-- 
Best regards,
Aleksander Alekseev



pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: New "single" COPY format
Next
From: Dilip Kumar
Date:
Subject: Re: Fix small typo, use InvalidRelFileNumber instead of InvalidOid