Re: pgAdmin4 not handling '\' characters properly

Wondering if this is a character set issue with your data? If you look at
the rows as shown in DBeaver or psql, the back slash "\" following the word
"Documents" in the file path appears the same for the first four result
rows from 2017 and the following rows from 2018. However the odd looking
character that shows in this same position in pdadmin seems to differ
(assuming it's byte pairs?). Looks like this might be a character set /
encoding issue. I believe database client encoding is set by default to
follow database encoding -- psql sets client encoding to auto, following
locale settings from your terminal -- or, apparently, you can override this
as needed (pgclientencoding). Depending on how the data got into your
system, I wonder if you may have differing encoding from different sources,
and whatever encoding pgadmin (and/or your client connection is set to when
using pgadmin) is using a different encoding interpretation than DBeaver
and psql.

Perhaps relevant:
https://stackoverflow.com/questions/36922248/how-do-i-change-the-default-client-encoding-in-postgres

https://www.postgresql.org/docs/9.3/multibyte.html

- Jon

On Thu, Jun 11, 2020 at 10:34 AM richard coleman <
rcoleman(dot)ascentgl(at)gmail(dot)com> wrote:

> Running pgAdmin4 version 4.22 on Windows 10 Enterprise Chromium browser it
> appears that pgAdmin is back to mangling character strings that contain the
> \ character. Instead of simply displaying it, it is improperly treating it
> as an escape character. As you can see from the below screen shots:
>
> psql:
> [image: tbl_documents_pgsql.png]
>
> pgAdmin4:
> [image: tbl_documents_pgAdmin4.png]
>
> dBeaver:
> [image: tbl_documents_dbeaver.png]
>
> Is there some setting to get pgAdmin4 to stop mangling the representation
> of my data.
>
> Thanks,
>
> rik.
>