| From: | richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com> |
|---|---|
| To: | dsbw <dsbw(at)protonmail(dot)com> |
| Cc: | "pgadmin-support(at)lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Import fails on single quote. |
| Date: | 2021-05-11 19:16:04 |
| Message-ID: | CAGA3vBtLWz8W3Wya_8z4enQjKv4=6AC98Jeo2C8+=cVtTz+p1g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Blake,
You might want to try escaping the single quotes in your data. Either by
doubling them up or switching double quotes for dollar-quoted strings.
Just a thought,
rik.
On Tue, May 11, 2021 at 3:02 PM dsbw <dsbw(at)protonmail(dot)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===
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aditya Toshniwal | 2021-05-12 05:05:36 | Re: Import fails on single quote. |
| Previous Message | dsbw | 2021-05-11 19:01:53 | Import fails on single quote. |