Re: Import/Export failure due to UTF-8 error in pgAdmin4 but not in pgAdmin3

Hi On Tue, Jan 8, 2019 at 12:47 AM richard coleman wrote: > > Dave, > > Thanks for taking the time to respond, but I don't see anywhere that > SQL_ASCII is recommended against doing. Here's the documentation listing the > supported encoding schemas: > https://www.postgresql.org/docs/current/mu

Re: Import/Export failure due to UTF-8 error in pgAdmin4 but not in pgAdmin3

Dave, Thanks for taking the time to respond, but I don't see anywhere that SQL_ASCII is recommended against doing. Here's the documentation listing the supported encoding schemas: https://www.postgresql.org/docs/current/multibyte.html . The *only* caveats listed for SQL_ASCII are: > In most case

Re: Import/Export failure due to UTF-8 error in pgAdmin4 but not in pgAdmin3

Hi On Mon, Jan 7, 2019 at 11:30 PM richard coleman wrote: > > Dave, > > I can't speak to Nania's specific issue, but I believe it's a pgAdmin4 > specific problem, at least in so far as SQL_ASCII is concerned. I say this > because I can usually work with the data just fine from the psql prompt,

Re: Import/Export failure due to UTF-8 error in pgAdmin4 but not in pgAdmin3

Dave, I can't speak to Nania's specific issue, but I believe it's a *pgAdmin4* specific problem, at least in so far as SQL_ASCII is concerned. I say this because I can usually work with the data just fine from the psql prompt, but *not* through pgAdmin4 (or other postgreSQL GUI's like dBeaver tha

Re: Import/Export failure due to UTF-8 error in pgAdmin4 but not in pgAdmin3

On Mon, Jan 7, 2019 at 9:11 PM richard coleman wrote: > > Nania, > > Welcome to the wonderful world of pgAdmin4. I have been bitten often by this > particular shortcoming in pgAdmin4. :( My issue seems to stems from the fact > that I use ASCII tables as a back end for a .Net windows applicatio

Re: Import/Export failure due to UTF-8 error in pgAdmin4 but not in pgAdmin3

Nania, Welcome to the wonderful world of pgAdmin4. I have been bitten often by this particular shortcoming in pgAdmin4. :( My issue seems to stems from the fact that I use ASCII tables as a back end for a .Net windows application and perfectly valid windows (Word/Excel) characters cause pgAdmin4

Import/Export failure due to UTF-8 error in pgAdmin4 but not in pgAdmin3

Hi, I am pretty new to PostgreSQL so I might just miss something basic here. My problem is that, I cannot import or export some of the tables in my db with pgAdmin4, as it raises the “ERROR: unvalid byte-sequenz for coding »UTF8«: 0xdf 0x67“”. The table was originally created with Excel and im

Re: Docker servers pre-loaded script is not executed.

Hi On Mon, Jan 7, 2019 at 1:33 AM Juan López wrote: > > Hi, > > I'm using the next docker-compose configuration: > > pgAdmin: > image: dpage/pgadmin4 > ports: > - "5050:80" > environment: > PGADMIN_DEFAULT_EMAIL: u...@domain.com > PGADMIN_DEFAULT_PASSWORD: secret > volumes: >