| From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
|---|---|
| To: | "Tatsuo Ishii" <ishii(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: New "raw" COPY format |
| Date: | 2024-10-13 12:39:54 |
| Message-ID: | 1fb4eba5-e894-49e1-a2a4-f4e360b02a0f@app.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Oct 13, 2024, at 11:52, Tatsuo Ishii wrote:
> After copy imported the "unstructured text file" in "row" COPY format,
> what the column type is? text? or bytea? If it's text, how do you
> handle encoding conversion if the "unstructured text file" is encoded
> in server side unsafe encoding such as SJIS?
>
>> All characters are taken literally.
>> There is no special handling for quotes, backslashes, or escape sequences.
>
> If SJIS text is imported "literally" (i.e. no encoding conversion), it
> should be rejected.
I think encoding conversion is still necessary,
and should work the same as for the COPY formats "text" and "csv".
/Joel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Junwang Zhao | 2024-10-13 14:43:22 | Re: general purpose array_sort |
| Previous Message | Thomas Krennwallner | 2024-10-13 12:28:57 | Re: pg_upgrade check for invalid databases |