Thread: backup improvements
There are a few things annoying me daily while working with backup feature. I believe improvements listed below would help a lot: 1. backup settings should be remembered by program for next use. Currently each time I want to do backup I need to set even such basic things as character set or format. Would be nice if all the last backup settings be set when next time use 2. Objects list is always scrolled to the bottom. I believe would be better when scrolled to the first selected item. Example scenario: I do RMB on some schema and select backup. It cause schema and its all objects are going to be selected on backup/objects list. But to check them I have to scroll the list up every time. Hope it will help with regards
On Mon, 2012-07-30 at 13:54 +0200, Michal Kozusznik wrote: > There are a few things annoying me daily while working with backup feature. > I believe improvements listed below would help a lot: > 1. backup settings should be remembered by program for next use. > Currently each time I want to do backup I need to set even such basic > things as character set or format. Would be nice if all the last backup > settings be set when next time use > I added a ticket for someone to work on this when he has time. > 2. Objects list is always scrolled to the bottom. I believe would be > better when scrolled to the first selected item. Example scenario: I do > RMB on some schema and select backup. It cause schema and its all > objects are going to be selected on backup/objects list. But to check > them I have to scroll the list up every time. > I don't get this. Or I'm not able to reproduce your issue. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com
probably you have too less schemas in database. we have about 40 schemas. one of them contain 200 tables. when i try to backupschema from top of the list, and go to object tab of backup window, object tree is scrolled down to the bottom so Icannot see schema intended to be backuped MK 30. 7. 2012 v 21:50, "Guillaume Lelarge" <guillaume@lelarge.info>: > On Mon, 2012-07-30 at 13:54 +0200, Michal Kozusznik wrote: >> There are a few things annoying me daily while working with backup feature. >> I believe improvements listed below would help a lot: >> 1. backup settings should be remembered by program for next use. >> Currently each time I want to do backup I need to set even such basic >> things as character set or format. Would be nice if all the last backup >> settings be set when next time use >> > > I added a ticket for someone to work on this when he has time. > >> 2. Objects list is always scrolled to the bottom. I believe would be >> better when scrolled to the first selected item. Example scenario: I do >> RMB on some schema and select backup. It cause schema and its all >> objects are going to be selected on backup/objects list. But to check >> them I have to scroll the list up every time. >> > > I don't get this. Or I'm not able to reproduce your issue. > > > -- > Guillaume > http://blog.guillaume.lelarge.info > http://www.dalibo.com >
Hello I have idea about one more improvement to be queued. After executing backup, Backup button turns into Done one (curious the Cancel button remains, can't imagine the reason since it has the same function than Done one). I suggest to leave the Backup button untouched making possible to execute another backup. It might be useful in case of dumping schema and data separately or just performing backups of single objects with the same settings. As reported earlier (there is some ticket about improvement) closing window make all backup settings lost, so possibility to execute next backup without closing backup wizard window would be very helpful. with regards On 31.7.2012 2:10, Kozusznik Michal wrote: > probably you have too less schemas in database. we have about 40 schemas. one of them contain 200 tables. when i try tobackup schema from top of the list, and go to object tab of backup window, object tree is scrolled down to the bottom soI cannot see schema intended to be backuped > > MK > > 30. 7. 2012 v 21:50, "Guillaume Lelarge" <guillaume@lelarge.info>: > >> On Mon, 2012-07-30 at 13:54 +0200, Michal Kozusznik wrote: >>> There are a few things annoying me daily while working with backup feature. >>> I believe improvements listed below would help a lot: >>> 1. backup settings should be remembered by program for next use. >>> Currently each time I want to do backup I need to set even such basic >>> things as character set or format. Would be nice if all the last backup >>> settings be set when next time use >>> >> I added a ticket for someone to work on this when he has time. >> >>> 2. Objects list is always scrolled to the bottom. I believe would be >>> better when scrolled to the first selected item. Example scenario: I do >>> RMB on some schema and select backup. It cause schema and its all >>> objects are going to be selected on backup/objects list. But to check >>> them I have to scroll the list up every time. >>> >> I don't get this. Or I'm not able to reproduce your issue. >> >> >> -- >> Guillaume >> http://blog.guillaume.lelarge.info >> http://www.dalibo.com >>
Yes, good idea! Also, blocking the UI during backups and restores is a pain. I often setup the backup in pgadmin but then execute it fromthe command line, so that my pgadmin doesn't block. (Or else I open a second instance of pgadmin so that I can continueto work while the backup or restore takes place.) -- John Abraham jea@hbaspecto.com On 2013-01-22, at 8:55 AM, Michal Kozusznik wrote: > Hello > I have idea about one more improvement to be queued. > After executing backup, Backup button turns into Done one (curious the Cancel button remains, can't imagine the reasonsince it has the same function than Done one). > > I suggest to leave the Backup button untouched making possible to execute another backup. > It might be useful in case of dumping schema and data separately or just performing backups of single objects with thesame settings. > As reported earlier (there is some ticket about improvement) closing window make all backup settings lost, so possibilityto execute next backup without closing backup wizard window would be very helpful. > > with regards > > On 31.7.2012 2:10, Kozusznik Michal wrote: >> probably you have too less schemas in database. we have about 40 schemas. one of them contain 200 tables. when i try tobackup schema from top of the list, and go to object tab of backup window, object tree is scrolled down to the bottom soI cannot see schema intended to be backuped >> >> MK >> >> 30. 7. 2012 v 21:50, "Guillaume Lelarge" <guillaume@lelarge.info>: >> >>> On Mon, 2012-07-30 at 13:54 +0200, Michal Kozusznik wrote: >>>> There are a few things annoying me daily while working with backup feature. >>>> I believe improvements listed below would help a lot: >>>> 1. backup settings should be remembered by program for next use. >>>> Currently each time I want to do backup I need to set even such basic >>>> things as character set or format. Would be nice if all the last backup >>>> settings be set when next time use >>>> >>> I added a ticket for someone to work on this when he has time. >>> >>>> 2. Objects list is always scrolled to the bottom. I believe would be >>>> better when scrolled to the first selected item. Example scenario: I do >>>> RMB on some schema and select backup. It cause schema and its all >>>> objects are going to be selected on backup/objects list. But to check >>>> them I have to scroll the list up every time. >>>> >>> I don't get this. Or I'm not able to reproduce your issue. >>> >>> >>> -- >>> Guillaume >>> http://blog.guillaume.lelarge.info >>> http://www.dalibo.com >>> > > > > -- > Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgadmin-support
On Tue, 2013-01-22 at 16:55 +0100, Michal Kozusznik wrote: > Hello > I have idea about one more improvement to be queued. > After executing backup, Backup button turns into Done one (curious the > Cancel button remains, can't imagine the reason since it has the same > function than Done one). > The reason is that we don't hide widgets. We could disable it of course... but you won't be able to use Escape to close the window. > I suggest to leave the Backup button untouched making possible to > execute another backup. > It might be useful in case of dumping schema and data separately or just > performing backups of single objects with the same settings. We changed the Backup button to a Done button, so that people know the backup was done and won't run another one IIRC. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com
On Tue, 2013-01-22 at 09:07 -0700, John Abraham wrote: > Yes, good idea! > > Also, blocking the UI during backups and restores is a pain. I often setup the backup in pgadmin but then execute it fromthe command line, so that my pgadmin doesn't block. (Or else I open a second instance of pgadmin so that I can continueto work while the backup or restore takes place.) > I don't remember which one, but one of them doesn't block the UI. The other does it though. I tried to pinpoint why, but didn't find yet. -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com
Unfortunately it proves that way you have chosen doesn't match best practices for creating UI. Besides, it makes impossible to execute backup once again with the same or slightly changed backup settings (what I alreadyprooved). Also I didn't ask form hide anything. I'm asking to leave it without changes. Instead of changing meanin of backup button,just pop up some modal requester with the information. 2 birds with one rock. MK 23. 2. 2013 v 19:33, "Guillaume Lelarge" <guillaume@lelarge.info>: > On Tue, 2013-01-22 at 16:55 +0100, Michal Kozusznik wrote: >> Hello >> I have idea about one more improvement to be queued. >> After executing backup, Backup button turns into Done one (curious the >> Cancel button remains, can't imagine the reason since it has the same >> function than Done one). >> > > The reason is that we don't hide widgets. We could disable it of > course... but you won't be able to use Escape to close the window. > >> I suggest to leave the Backup button untouched making possible to >> execute another backup. >> It might be useful in case of dumping schema and data separately or just >> performing backups of single objects with the same settings. > > We changed the Backup button to a Done button, so that people know the > backup was done and won't run another one IIRC. > > > -- > Guillaume > http://blog.guillaume.lelarge.info > http://www.dalibo.com >
On Sat, 2013-02-23 at 18:48 +0000, Kozusznik Michal wrote: > Unfortunately it proves that way you have chosen doesn't match best practices for creating UI. That's probably not the only one bad choice in UI on pgAdmin :) > Besides, it makes impossible to execute backup once again with the same or slightly changed backup settings (what I alreadyprooved). Yeah, I understand that. Changing the button behaviour will get against some other users wishes, and so won't happen. Having the dialog remember the old values is something I would like to see coming though. > Also I didn't ask form hide anything. I'm asking to leave it without changes. Instead of changing meanin of backup button,just pop up some modal requester with the information. 2 birds with one rock. > Well, the "hide a button" came from your comment: "curious the Cancel button remains". -- Guillaume http://blog.guillaume.lelarge.info http://www.dalibo.com