Bob Davenport I’ve changed back to open as its not fixed till the release is available. The only other solution given was to downgrade to an older version of MySQL Workbench – 6.1.7.Īn excerpt of the comments show several users’ reactions to the bug report having been closed with no solution offered:
A user has devised a workaround that involves installing his build of MySQL Workbench, but that is not ideal in many production environments, for obvious security concerns. It is interesting that Oracle has closed the official bug report, despite the fact that no patch or new version is available.
It took quite a bit of searching to find this – apparently not too many folks have encountered this problem as yet – but I did find confirmation on Stack Overflow that this is now a known issue, and that the next release should have it fixed.
0 kommentar(er)
