From: | Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com> |
---|---|
To: | mapsware(at)prodigy(dot)net(dot)mx |
Cc: | "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Problem with encoding (display wrog characters) |
Date: | 2018-10-17 03:44:39 |
Message-ID: | CAFOhELf=iSpxU5d6HHYLgWNhLtcwnhXqWsh__0Vd=kQft3rQmw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Wed, Oct 17, 2018 at 4:06 AM Martin Paredes <mapsware(at)prodigy(dot)net(dot)mx>
wrote:
>
> Server: PostgreSQL 9.3.5 on FreeBSD 10.0
> Client: pgAdmin4 v3.4 on Windows 7 Profesional 64 bits
>
> The database is LATIN1, when I run the next query
>
> SELECT nom_usr FROM public.usuarios WHERE id_usr = 8;
>
> in psql (in the server), it is displayed correctly
>
> ACUÑA AARON
>
> But in pgAdmin the display is wrong (Ñ is converted to 2 characters)
>
> ACUÑA AARON
>
> When I consult the encoding inside of pgAdmin with
>
> SHOW client_encoding;
>
> It shows
>
> UNICODE
>
> If I run the next command in a consult in pgAdmin
>
> SET client_encoding = 'LATIN1';
> SELECT * FROM public.usuarios WHERE id_usr = 8;
>
> It display correctly
>
> ACUÑA AARON
>
> Is python assuming that because the database is in LATIN1, the
> character arrive in LATIN1?
>
> Any ideas about what is happening?
>
> Please report this bug @
https://redmine.postgresql.org/projects/pgadmin4/issues
>
> --
> Martin Paredes
> Hermosillo, Son. Mexico
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Hibbard, Brandon | 2018-10-17 12:52:01 | RE: v3.3 Auto complete broken |
Previous Message | Martin Paredes | 2018-10-16 22:36:22 | Problem with encoding (display wrog characters) |