| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Joel Jacobson <joel(at)compiler(dot)org> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Should CSV parsing be stricter about mid-field quotes? |
| Date: | 2024-10-09 16:14:24 |
| Message-ID: | 6982dfa1-b784-49ba-b7c7-d2a8be0f77a6@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2024-10-09 We 11:58 AM, Tom Lane wrote:
> "Joel Jacobson" <joel(at)compiler(dot)org> writes:
>> I think it would be nicest to introduce a new "raw" FORMAT,
>> that clearly get things right already at the top-level,
>> instead of trying to customize any of the existing formats.
> FWIW, I like this idea. It makes it much clearer how to have a
> fast parsing path.
>
>
WFM, so something like FORMAT {SIMPLE, RAW, FAST, SINGLE}? We don't seem
to have an existing keyword that we could sanely reuse here.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2024-10-09 16:16:31 | Re: Avoid possible overflow (src/port/bsearch_arg.c) |
| Previous Message | Tom Lane | 2024-10-09 15:58:45 | Re: Should CSV parsing be stricter about mid-field quotes? |