Bug #59215 | Not saving the SQL History files | ||
---|---|---|---|
Submitted: | 29 Dec 2010 16:11 | Modified: | 1 Sep 2011 19:48 |
Reporter: | David Muoz Vicente | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 5.2.31 | OS: | Windows (XP SP3) |
Assigned to: | CPU Architecture: | Any |
[29 Dec 2010 16:11]
David Muoz Vicente
[27 Apr 2011 15:21]
Armando Lopez Valencia
Defect Verified on windows XP with Workbench 5.2.33b. It is not showing an error message anymore BUT workbench is not creating the history files. Repro Steps: 1. Create a windows account with the special character "ñ" within the name. 2. Open Workbench. 3. Open the SQL Editor. 4. Execute a couple of querys (select * from world.city). 5. Go to output tab. 6. Select "History" from the "Show output from" tab. 7. Verify the History Log. 8. Close Workbench. 9. Repeat steps 2-7. Expected Results: The history Logs from the last session must appear. Actual results: No logs from the last session appears. Note: If you go to: "C:\Documents and Settings\[User with "ñ"]\Application Data\MySQL\Workbench\sql_history\" you will notice that no history files are created.
[1 Sep 2011 19:48]
Philip Olson
Fixed as of 5.2.35: + The SQL Editor <guilabel>History</guilabel> could not be saved + when the username contained Unicode characters. This was due to + &workbench; attempting to save files using an invalid file path.