MySQL Bugs: #75456: Changing the MySQL Connection name resets cache/

Bug #75456	Changing the MySQL Connection name resets cache/
Submitted:	9 Jan 2015 3:19	Modified:	9 Jan 2015 5:39
Reporter:	Philip Olson	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	6.2.4	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Renaming a MySQL connection causes the cache/ information to reset. This includes the *.column_width and *.cache files.

I did not test every possible aspect of this but do notice that the cached sql_workspaces/connection_name-n.workspace/schema_tree information is preserved after the rename, so this issue might be specific to cache/*.

How to repeat:
1. Create a MySQL connection
2. Open the connection and execute a SELECT query
3. View the results and change a column width in the results grid
4. View the associated cache/connection_name.column_widths file
5. View the associated cache/connection_name.cache file
6. Change the MySQL connection name that was created in step #1
7. Open this MySQL connection
8. Note that the cached data was reset e.g. cache/old.column_widths differs from cache/new.column_widths

I tested this on Workbench 6.2.4 / OS X

Suggested fix:
Preserve the values.

Hello Philip Olson,

Thank you for the report and repeatable test case.
Observed similar behavior on Win7 with WB 6.2.4.

Thanks,
Umesh