Some pgAdmin 4 (4.1) bugs

From: Arni Kromić <arni(dot)kromic(at)bios-ict(dot)hr>
To: pgadmin-support(at)lists(dot)postgresql(dot)org
Subject: Some pgAdmin 4 (4.1) bugs
Date: 2019-01-29 09:54:32
Message-ID: 1d2c16d6-0cfa-c8b9-c0cc-1584fad3a362@bios-ict.hr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Hello everybody. Before everything, I'd like to thank pgAdmin devs for
all the great work!

So, I've upgraded pgAdmin yesterday, and I've noticed a bug i haven't
noticed before, so I thought I should mention it, together with a couple
of bugs I've already encountered before.

The new bug is in the UI, specifically in the query "window". While the
lower half which contains "Data Output", "Explain" etc. can be undocked
from its position and become a floating window, it cannot be docked
back. If I undock single items ("DataOutput" etc.) from that window, I
can dock them one by one back to the original position, but not the
entire window.

It's annoying because it can happen when you try to resize the top of
the window; you can easily miss the thin line (changing cursor to
double-arrow) and hit the "top bar" of that window and yank it out of
its docking position - this is how I found out. Since it can't be
returned to its original position as it is, you need to drag all four
tabs one by one back to the position. Specifically, if you enter a
negative Increment, p

The other bug I've noticed before concerns the "Create - Sequence"
functionality. If I enter a negative Increment, it complains:
"Increment' must be greater than or equal to 1." Since Postgres does
accept negative increments (i.e. descending sequences). This is strange,
since descending sequences ARE mentioned in the help; if there is a way
to specify them, I haven't found it...

There is also a minor (possible) bug in the "Create - Function /
Procedure" dialog - when you enter code in the window, the resulting SQL
is something like "AS $BODY$select this from that$BODY$;". While it
doesn't affect functionality, the readability of the CREATE code is, so
I prefer to put newlines on the first and last lines of Code input.
There is one example where the code is somewhat messed up though, and
that's when the last line of code is a comment. Then the resulting SQL
contains something like this:

AS $BODY$select this from that
--comment$BODY$;

The closing $BODY$ thus gets commented out.

Another glitch new to 4.1 is that SQL tab is not visible when a new
"Create - Function / Procedure" window is open - it has to be widened a
bit for that tab to show. Also there is no indication that tab exists -
if I didn't expect it to be there, I wouldn't've even tried looking for it.

Please tell me if those issues should be or have been reported, and
should I do it (and where) or someone else would. Thank you for your
patience!

--
Kind Regards,
Arni Kromić

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Khushboo Vashi 2019-01-29 10:35:14 Re: Some pgAdmin 4 (4.1) bugs
Previous Message Diego Augusto Molina 2019-01-29 05:41:34 Re: Docker image not running on IPv6-disabled systems