Bug #64286 Changing default path when exporting db to a self contained file reports a bug

Submitted: 9 Feb 2012 22:23 Modified: 10 Mar 2012 4:55
Reporter: Robert Sanford Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Administration Severity:S3 (Non-critical)
Version:5.2.37 OS:Windows (XP)
Assigned to: CPU Architecture:Any

[9 Feb 2012 22:23] Robert Sanford
Description:
When requesting to export a schemata to a self-contained file, the Workbench Administration sub-system reports a bug after attempting to change the default path. Note: If you ignore the message, and then change the path, you can start the export operation.

How to repeat:
Using the Administrator, select Data Export, then from the Object Selection tab, select a single schemata. Next, select all of the objects from the selected schemata. From the Options section, select Export to a Self-Contained File. Click the ... button on the right to change the destination path. A dialog box immediately pops up stating "Workbench has encountered a problem. The path is not of a legal form." The Object Selection section is cleared and a red X is displayed through both halves of the section.
[9 Feb 2012 22:49] Robert Sanford
Changed the synopsis from "Requesting to the path ..." to "Changing default path..."
[10 Feb 2012 1:18] MySQL Verification Team
I couldn't repeat on Windows 7 64-bits.
[10 Feb 2012 4:55] Valeriy Kravchuk
Looks similar to Bug #64267. Please, check.
[11 Mar 2012 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.054 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.