Re: Should CSV parsing be stricter about mid-field quotes?

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: "Joel Jacobson" <joel(at)compiler(dot)org>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Should CSV parsing be stricter about mid-field quotes?
Date: 2024-10-10 08:37:47
Message-ID: 0e0ce40e-819f-46d8-99d4-251524e9e0e8@manitou-mail.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joel Jacobson wrote:

> - No Headers or Metadata:

It's not clear why it's necessary to disable the HEADER option
for this format?

> The format does not support header rows or end-of-data markers;
> every line is treated as data.

With COPY FROM STDIN followed by inline data in a script,
an end-of-data marker is required. That's also a problem
for CSV except it's mitigated by the possibility of quoting
(using "\." instead of \.)

Best regards,
--
Daniel Vérité
https://postgresql.verite.pro/
Twitter: @DanielVerite

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2024-10-10 08:40:57 Re: ALTER TABLE ONLY .. DROP CONSTRAINT on partitioned tables
Previous Message Fredrik Widlert 2024-10-10 08:24:29 Re: Pg17 Crash in Planning (Arrays + Casting + UDF)