Re: pgAdmin 4 V4.2 and non-unicode database

2019-02-11 Thread Zoltán Sörös
he OS on which that >>> operation is executed. >>> >>> >>> >>> Hope it helps. >>> >>> Regards >>> >>> >>> >>> *From:* Zoltán Sörös [mailto:zso...@gmail.com] >>> *Sent:* vendredi 8 février 201

Re: pgAdmin 4 V4.2 and non-unicode database

2019-02-09 Thread Akshay Joshi
rds >> >> >> >> *From:* Zoltán Sörös [mailto:zso...@gmail.com] >> *Sent:* vendredi 8 février 2019 14:23 >> *To:* pgadmin-support@lists.postgresql.org >> *Subject:* pgAdmin 4 V4.2 and non-unicode database >> >> >> >> Hi! >> >> &g

Re: pgAdmin 4 V4.2 and non-unicode database

2019-02-08 Thread Zoltán Sörös
ecuted. > > > > Hope it helps. > > Regards > > > > *From:* Zoltán Sörös [mailto:zso...@gmail.com] > *Sent:* vendredi 8 février 2019 14:23 > *To:* pgadmin-support@lists.postgresql.org > *Subject:* pgAdmin 4 V4.2 and non-unicode database > > > > Hi! > >

RE: pgAdmin 4 V4.2 and non-unicode database

2019-02-08 Thread Mathias Zajaczkowski
@lists.postgresql.org Subject: pgAdmin 4 V4.2 and non-unicode database Hi! Our database uses latin2 encoding. pgAdmin V4 displays all text correctly, but when I copy something from the SQL tab to the query tool, and run the query, it scrambles all accented letters in the stored texts, notably on

pgAdmin 4 V4.2 and non-unicode database

2019-02-08 Thread Zoltán Sörös
Hi! Our database uses latin2 encoding. pgAdmin V4 displays all text correctly, but when I copy something from the SQL tab to the query tool, and run the query, it scrambles all accented letters in the stored texts, notably on comments on columns and texts in stored functions. This problem exists s