Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Suggestion for copy database

forums forums SQLyog SQLyog: Bugs / Feature Requests Suggestion for copy database

  • This topic is empty.
Viewing 4 reply threads
  • Author
    Posts
    • #8874
      JPV
      Member

      Hello,

      I am using SQLYog for over a year now and I think it is a great tool, but I think it can become even better.

      I would like to propose a new form design for the copy database window. The current form design is not well designed in my opinion because it is easy to make mistakes, which is not nice when you are copying a whole database. If you want to copy a database from one host to another, you have to have two connections open. The host in the active child window will be used as source; when by accident the wrong child window is active you will use the wrong host as source, but in the copy database window you cannot see which host is the source and so you cannot see if you selected the wrong source host by accident. Next when you select the target, you have to select it from a dropdown listbox filled with a list of database names followed by the user/hostname. This list is sorted alphabetically by database name, while it is better to have a list grouped by host and within sorted by database name.

      Why not the following form design:

      – one form with two parts: the source on the left and the target on the right

      – both parts have a dropdown listbox to select the host

      – below, both parts have a list with database names from the selected host, sorted alphabetically

      In my opinion the advantages are:

      – it is very clear which source host is used

      – it is very clear which target host is used

      – the risc to select something wrong by accident is reduced to a minimum

      – the general layout will be much more intuitive

      alternatively, the combination of host dropdown list box and database list can be replaced by a tree view, with the hosts on the upper level and their databases on the lower level.

      I am willing to provide a graphic design to explain what I mean, if you want me to.

      I am very well aware of the fact that the copy database option functions properly, but I think that a new form design will make it easier to use, with less chance for errors.

      I hope you will consider my suggestion above and that it will lead to an sqlyog that will become even better than it is now.

    • #17244
      Ritesh
      Member

      First of all, thank you for your valuable time and we are absolutely delighted to have so many well-wishers for SQLyog!

      We would like to take this forward and target it for Rel 4.2. Please send your design and we can discuss it on the forum. We are committed towards providing the most intuitive UI to MySQL.

      All Webyog forum members are welcome to improvise on the UI design.

      Additionally, please send a mail to [email protected] if you want to become a beta-tester for SQLyog.

    • #17245
      JPV
      Member

      I posted my design earlier but apparently it did not appear in the forum, so now I try it again. The design is for a window with easier database copying, without confusion about source and target. Consider this to be a first sketch and I am curious about your response!

    • #17246
      Ritesh
      Member

      In the Tables list window, do you propose to show tables of Database 1 or Database 2?

    • #17247
      JPV
      Member

      Sorry, haven't been here for a while… I guess the notification for new replies didn't work…

      Good question… Of course the tables should be of the source database. But you don't know what the source database will be until you press one of the copy buttons… and that's too late. Perhaps it is possible to make database 1 the source and database 2 the destination, with one copy button (from left to right, of course) and have an extra button that switches the source and the destination, and that will reload the tables list.

Viewing 4 reply threads
  • You must be logged in to reply to this topic.