Bug #82843 | MySQL Workbench fails to connect because of incorrect LastDefaultSchema escaping | ||
---|---|---|---|
Submitted: | 2 Sep 2016 10:21 | Modified: | 3 Sep 2016 6:46 |
Reporter: | Rob Janssen | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.0 - 6.3.7 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[2 Sep 2016 10:21]
Rob Janssen
[2 Sep 2016 10:37]
Rob Janssen
Step 3 should read: 3. Close MySQL Workbench >>and reopen it<< and use the same stored connection as used in step 2 But I'm pretty sure that was clear ;-)
[3 Sep 2016 6:46]
MySQL Verification Team
Hello Rob Janssen, Thank you for the report. Observed this with WB 6.3.7 on Win7. Thanks, Umesh
[24 Oct 2019 9:46]
Simon Vacker
Issue still exists in 8.0.17
[28 Jan 2023 0:49]
B K
Problem still present in Workbench v8.0. My LastDefaultSchema was set to 2022. While editing the connection, Test Connection worked. Open Connection from Home page did not. Delimited the 2022 with double quotes and the connection opens.