| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Nanina Tron <nanina(dot)tron(at)icloud(dot)com> |
| Cc: | richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com>, "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Import/Export failure due to UTF-8 error in pgAdmin4 but not in pgAdmin3 |
| Date: | 2019-01-08 17:15:39 |
| Message-ID: | CA+OCxoze+nZeBJmyNUFJeqct=C1mRVtBbdp+=OTTrWpBmXZiXA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Tue, Jan 8, 2019 at 8:55 PM Nanina Tron <nanina(dot)tron(at)icloud(dot)com> wrote:
>
>
> Hi,
>
> yes thank you I will scan the table so at least I will see the 'bad' characters. We will see how many there are.
> Sorry, i forgot to append the data.
Thanks. Did that include the "bad" data? I can load it just fine into
a SQL_ASCII database (which I'd expect, as there's no encoding
checks), or a UTF-8 database, and I can successfully export the table
in both cases.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick De Visschere | 2019-01-08 20:07:15 | Re: Change browser in MacOS |
| Previous Message | Dave Page | 2019-01-08 17:07:36 | Re: Import/Export failure due to UTF-8 error in pgAdmin4 but not in pgAdmin3 |