forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Bug : Correct Mysql Connection Not Used / Shown When Editing An "s
- This topic is empty.
-
AuthorPosts
-
-
June 30, 2012 at 12:00 pm #12731DistinctiveMember
Problem:
I am using SQLyog's export data function to preform scheduled backups of databases across two servers.
When I “Edit a saved job” using the “Scheduled backups” function, when presented with the “Provide details about your MySQL server” screen, instead of displaying the details contained within the XML job file, instead the connection details for the last used MySQL server are displayed.
This can be dangerous, when I edit the job's XML file, this might inadvertantley cause me to use the wrong database server for the backup, either:
- causing the backup to fail,
- if both servers have a database with the same name as the one that I am trying to back up, I might back up my data from the wrong server!
or
Current behaviour:
The “Export Data As Batch Script Wizard” does not display the MySQL connection details that were saved within the job's XML file, instead it displays the last used connection details.
Expected behaviour:
The “Export Data As Batch Script Wizard” should display the MySQL connection details that are saved within the job's XML file, it should NOT display the last used MySQL connection.
Reproducable: Always
Steps to reproduce:
- Ensure that SQLyog has two saved connections to MySQL servers.
- Click [Menu] > [Powertools] > [Scheduled Backups…]
- Create a first job, select “Start a new job”, select the first MySQL server, and create a backup job and save it to an XML file.
- Click [Menu] > [Powertools] > [Scheduled Backups…]
- Create a second job, select “Start a new job”, select the second MySQL server, and create a backup job and save it to an XML file (you will notice that the configuration screen remembers the last used MySQL connection, which is a nice feature).
- Click [Menu] > [Powertools] > [Scheduled Backups…]
- Select “Edit a saved job” and use the FIRST job that was created, then click next.
- On the MySQL connection screen you'll notice that the details displayed in the connection are of the last used connection, not the connection that was saved inside the job's XML file.
- You'll notice that despite the wrong MySQL server information being displayed, the correct database name is still displayed in the “Database” field.
- But when you select the correct connection from the “Copy connection from” field, the database name will be erased.
- Also take note that if by co-incidence the displayed selected MySQL server also has a database with the same name, the user might accidentally click [Next] without realising that the wrong database server is selected, causing them to back up the wrong data!
I wouldn't call this a critical bug, but I can certainly see it as being something that would cause people grief, especially if the result of the bug is that it causes someone accidentally back up the wrong database.
-
-
AuthorPosts
- You must be logged in to reply to this topic.