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

From: Zoltán Sörös <zsoros(at)gmail(dot)com>
To: Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com>, pgadmin-support(at)lists(dot)postgresql(dot)org
Subject: Re: pgAdmin 4 V4.2 and non-unicode database
Date: 2019-02-11 09:51:30
Message-ID: CAFiqkXjo8ZrP+BPCsUu2cDA5QH1x3bf3n0w9qa7qjJ6TevAn5Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Greetings,
issue created: https://redmine.postgresql.org/issues/3979

I've given it high priority because this bug corrupts inserted data as
well.
(FYI: no copy-paste this time, I've typed all commands into pgAdmin 4 V4.2.)

Sincerelly,
Zoltán Sörös

Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> ezt írta (időpont: 2019. febr.
10., V, 5:36):

> Hi Zoltan
>
> Please create a new RM https://redmine.postgresql.org/projects/pgadmin4
>
> On Sat, 9 Feb 2019, 11:14 Zoltán Sörös <zsoros(at)gmail(dot)com wrote:
>
>> Hey Mathias, I know pgAdmin is free and you make this for free and all
>> that, but *please* don't make me a fool. Sure, encoding can change during
>> copy and paste, but
>> 1) pgAdmin V3.6 works OK, as I mentioned
>> 2) All other software works OK
>>
>> So, would you please check the query tool source for a missing
>> set-database-encoding?
>>
>> Thanks.
>>
>> Mathias Zajaczkowski <mathias(dot)zajaczkowski(at)ubik(dot)ch> ezt írta (időpont:
>> 2019. febr. 8., P, 15:58):
>>
>>> Hi Soros,
>>>
>>>
>>>
>>> During copy/paste operation the encoding can change.
>>>
>>> It has nothing to do with pgAdmin but with the OS on which that
>>> operation is executed.
>>>
>>>
>>>
>>> Hope it helps.
>>>
>>> Regards
>>>
>>>
>>>
>>> *From:* Zoltán Sörös [mailto:zsoros(at)gmail(dot)com]
>>> *Sent:* vendredi 8 février 2019 14:23
>>> *To:* pgadmin-support(at)lists(dot)postgresql(dot)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 comments on columns and texts in stored functions. This problem
>>> exists since V4.0 - 3.6 was OK.
>>>
>>>
>>>
>>> Version: pgAdmin 4 V4.2, Windows 10, firefox browser
>>>
>>>
>>>
>>> Steps to reproduce:
>>>
>>> - create a database with latin2 encoding:
>>>
>>> create database mytemp encoding='LATIN2' lc_collate='hu_HU'
>>> lc_ctype='hu_HU';
>>>
>>> - create a table
>>>
>>> create table mytemptable (id integer not null, tempdata text);
>>>
>>> - create a comment on the database using latin2 encoding
>>>
>>> comment on table mytemptable is 'Árvíztűrő tükörfúrógép';
>>>
>>> - copy the comment command from the SQL tab of pgAdmin4 v4.2
>>>
>>> - paste the copied command into pgAdmin 4 v4.2 query tool
>>>
>>> - run the copied command
>>>
>>> - refresh the SQL tab of pgAdmin 4, and check comment on the table:
>>>
>>> COMMENT ON TABLE public.mytemptable IS 'à rvíztŹrő
>>> tĂźkĂśrfĂşrĂłgĂŠp';
>>>
>>>
>>>
>>> I'm not sure this plain text e-mail can display the problem, I can make
>>> screenshots if requested.
>>>
>>>
>>>
>>> Thanks in advance:
>>>
>>> Zoltán Sörös
>>>
>>

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Fabian Sturm 2019-02-11 12:54:23 pgAdmin 4 MacOS with client-certificates: on import qsql does not set the required sslcert and sslkey
Previous Message Khushboo Vashi 2019-02-11 04:47:53 Re: Please make these modifications to the Open dialog for the Query Tool