Re: ERROR: invalid byte sequence for encoding

2018-02-21 Thread André Burkhardt
Murtuza Zabuawala >> EnterpriseDB: http://www.enterprisedb.com >> The Enterprise PostgreSQL Company >> >> >> On Mon, Jan 15, 2018 at 5:57 PM, André Burkhardt < >> andre.burkha...@uni-jena.de> wrote: >> >>> Hi, >>> >>> -

Re: PgAdmin4.2.1 - ERROR: invalid byte sequence for encoding "UTF8": 0x00

2018-01-17 Thread Khushboo Vashi
Hi, Please log your bug at https://redmine.postgresql.org/projects/pgadmin4 Also, provide the steps to reproduce the issue with some test data. Thanks, Khushboo On Wed, Jan 17, 2018 at 11:55 AM, Pierre Wante wrote: > Bonjour, > > > > J’ai installé PgAdmin 4.2.1 sur mon P.C (Windows 7 64 Bits

PgAdmin4.2.1 - ERROR: invalid byte sequence for encoding "UTF8": 0x00

2018-01-17 Thread Pierre Wante
Bonjour, J’ai installé PgAdmin 4.2.1 sur mon P.C (Windows 7 64 Bits). Je me connecte à un serveur Cent-OS 7 avec PostgreSQL 10.1. Ma base de données contient une structure sans données. Je clique sur une table, puis sur l’onglet SQL afin de visualiser la définition de l’objet et j’obtiens l’erreu

Re: ERROR: invalid byte sequence for encoding

2018-01-15 Thread André Burkhardt
; On Mon, Jan 15, 2018 at 5:57 PM, André Burkhardt < > andre.burkha...@uni-jena.de> wrote: > >> Hi, >> >> Original-Nachricht >> Betreff: Re: ERROR: invalid byte sequence for encoding >> Von: Murtuza Zabuawala >> An: André Burkhardt >

Re: ERROR: invalid byte sequence for encoding

2018-01-15 Thread Murtuza Zabuawala
reSQL Company > > > > > > On Mon, Jan 15, 2018 at 4:24 PM, André Burkhardt < > > andre.burkha...@uni-jena.de> wrote: > > > >> We are using pgAdmin 4 2.0/2.1. Allmost all of our databases using > >> Encoding LATIN1. We have the problem, that when w

Re: ERROR: invalid byte sequence for encoding

2018-01-15 Thread Murtuza Zabuawala
wrote: > We are using pgAdmin 4 2.0/2.1. Allmost all of our databases using > Encoding LATIN1. We have the problem, that when we want to show a table > definition in the SQL-Tab, an error message pops up: > > Error retrieving the information - INTERNAL SERVER ERROR > ERROR: invalid by

ERROR: invalid byte sequence for encoding

2018-01-15 Thread André Burkhardt
We are using pgAdmin 4 2.0/2.1. Allmost all of our databases using Encoding LATIN1. We have the problem, that when we want to show a table definition in the SQL-Tab, an error message pops up: Error retrieving the information - INTERNAL SERVER ERROR ERROR: invalid byte sequence for encoding