| From: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(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-12 05:05:36 |
| Message-ID: | CAM9w-_=VXdX0anWGXH_3gsR3EJjneGkgmmbKOR_ePz2UCQThOg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Hi Dsbw,
Did you try changing the escape field ? It is by default a single quote.
[image: image.png]
On Wed, May 12, 2021 at 12:32 AM 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===
>
--
Thanks,
Aditya Toshniwal
pgAdmin hacker | Sr. Software Engineer | *edbpostgres.com*
<http://edbpostgres.com>
"Don't Complain about Heat, Plant a TREE"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | dsbw | 2021-05-12 05:13:30 | Re: Import fails on single quote. |
| Previous Message | richard coleman | 2021-05-11 19:16:04 | Re: Import fails on single quote. |