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

2019-02-08 Thread Zoltán Sörös
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 missin

RE: pgadmin 4.2 on Windows can’t reach this page 127.0.0.1:64729

2019-02-08 Thread Edouard Perov
The issue is resolved by specifying Chrome as a browser "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --app=%URL% From: Edouard Perov [mailto:edouard.pe...@ca.abb.com] Sent: Friday, February 8, 2019 1:08 PM To: pgadmin-support@lists.postgresql.org Subject: pgadmin 4.2 on Windows ca

Please make these modifications to the Open dialog for the Query Tool

2019-02-08 Thread Patrick Headley
I appreciate the GUI updates that were made to the Query Tool in v4.2. Here's a new request. Using pgAdmin4 v4.2 in Windows 7 running in desktop mode. In the query tool, when I attempt to open a saved script, the Name column in the Open Dialog isn't wide enough and it can't be adjusted. I trie

pgadmin 4.2 on Windows can’t reach this page 127.0.0.1:64729

2019-02-08 Thread Edouard Perov
Hi, I have just installed pgadmin 4.2 on Windows 10. When it is started it up, it launches a browser trying to connect to 127.0.0.1:64729 and returns the error “Hmmm...can’t reach this page”. I need to run pgadmin on Windows and access PostgressSQL on Linux. Thanks, Edouard

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

2019-02-08 Thread Mathias Zajaczkowski
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:zso...@gmail.com] Sent: vendredi 8 février 2019 14:23 To: pgadmin-support@lists.pos

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