From: | Adam Scott <adam(dot)c(dot)scott(at)gmail(dot)com> |
---|---|
To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Patch: New field in frmMain statusbar |
Date: | 2015-09-13 15:19:35 |
Message-ID: | CA+s62-Ous9Dr7EFGfwEh-N7xZGh8f173uUU=VbzzgV9crVD4NQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Hi,
please consider this patch to frmMain.
Situation: When a user has a large number of databases and connections,
when they select a table or other object in the Object browser tree, they
can lose track of which connection and database the object belongs too.
This makes it really easy for the user to make a mistake and drop an object
on the wrong connection (such as on a Production server instead of a
Development server). Also as a user is browsing multiple databases and
connections they can lose track of which object they are working on.
Solution: This patch adds a new field in the status bar of the main window
(frmMain), between the two other fields, keeping them the same. If there's
a currently selected object the field will display it's connection and
database. If there's no currently selected object, it will be blank.
Here's the danger, if we display the wrong connection and database, the
user could drop the wrong object. So it's imperative this never has a
bug. This code change is so small with so little dependencies, it relies
on already used code for such a long time that if it had a bug, then there
are other bigger bugs in the code that would have already shown up.
Regards,
Adam C. Scott
patch generated using Tortoise Git Create Patch Serial
Attachment | Content-Type | Size |
---|---|---|
0001-Adds-new-field-in-frmMain-statusbar-used-to-display-.patch | application/octet-stream | 1.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | John Obaterspok | 2015-09-13 19:37:58 | [PATCH] Add Commit/Rollback toolbar action version 2 |
Previous Message | Prasad Somwanshi | 2015-09-08 18:53:34 | Re: pgadmin4 setup.py, first time run |