Probably because of the number on the end. So its failing on the end of words, and a number on the end, still equals on the end of a word (to Postgres).
Bobb From: dsbw <d...@protonmail.com> Reply-To: dsbw <d...@protonmail.com> Date: Thursday, May 13, 2021 at 1:45 PM To: "pgadmin-support@lists.postgresql.org" <pgadmin-support@lists.postgresql.org> Subject: Re: Import fails on single quote. Think Before You Click: This email originated outside our organization. OK, it's not as straightforward as an unpaired single quote. I just had one fail on: "PET'1'" So the single quote is paired, and caused the problem. So I changed it to "PET 1"...and the whole import worked. But I got suspicious and started looking at the data for single quotes and found things like "T'BIRD", "B--CH'N!!" and "JOHN'S WIFE" and those all worked. So I'm not sure what the deal is. Sent with ProtonMail<https://protonmail.com/> Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, May 11th, 2021 at 12:01 PM, dsbw <d...@protonmail.com> wrote: Hello, Trying to import data, tab-delimited but unfortunately with quotes around string fields anyway. Like: 1234<tab>"JOHN"<tab>"SMITH"<tab>5678 PGAdmin import fails when the quoted value contains a single quote: 1234<tab>"EMPLOYEES'"<tab>"CREDIT UNION"<tab>5678 So the trailing quote (for possessive) after "EMPLOYEES" trips it up. Seems like, if one is inside a set of double-quotes, any single quotes should be ignored? (I know CSV is multiply and contradictorily defined, but still.) ===Blake===
