| Bug #60975 | Default schema isn't stored permanently for a stored connection | ||
|---|---|---|---|
| Submitted: | 26 Apr 2011 6:57 | Modified: | 17 Nov 2011 17:40 |
| Reporter: | Christian Rudolph | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
| Version: | 5.2.34 CE | OS: | Windows |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | default schema | ||
[26 Apr 2011 6:57]
Christian Rudolph
[26 Apr 2011 7:10]
Christian Rudolph
I just figured out, that it is enough to create a new model, press Synchronize Model, select a connection with a default schema and press "Next". After pressing "Next", the default schema is already lost, also if you abort the synchronization.
[26 Apr 2011 15:37]
MySQL Verification Team
Thank you for the bug report.
[9 Oct 2011 3:35]
Alfredo Kojima
I can't repeat this. I tried: - set a default schema to a connection in Manage Connections window - Create New Model - Pick Database -> Synchronize Model - cancel - Go back to Manage Connections window and see that the connection still has the default schema set Am I missing something?
[9 Oct 2011 7:00]
Christian Rudolph
I think the missing point is, that you need to click once on the next button, wenn you synchronize the model. The sequence should be - Pick Database -> Synchronize Model -> select the stored connection -> click next -> click cancel - go back to Manage Connections window So you need to execute step 2, Connect to DBMS in the synchronization wizard.
[9 Oct 2011 15:56]
Alfredo Kojima
Got it when I created a new connection in the same session.
[17 Nov 2011 17:40]
Philip Olson
Fixed as of 5.2.36: + The default schema selection would be lost after synchronizing a + model.
