[ODBC-215] MySQL Workbench removed after ODBC driver update Created: 2019-01-29  Updated: 2019-01-30  Resolved: 2019-01-30

Status: Closed
Project: MariaDB Connector/ODBC
Component/s: General
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: IT Particip Assignee: Lawrin Novitsky
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Windows 10


 Description   

After updating the MariaDB ODBC driver, it seems that MySQL Workbench is not available anymore on my computer. I think it is the second time that happened.

Even though it is not a major problem and it can be easily solved by installing MySQL Workbench again, it is pretty uncomfortable having to do that every time we update the driver. Above all because my boss uses it too.

Not sure if the installation of the driver can be customized in order to prevent this from happening, or if there is actually no workaround.

Can you sheed some light on this issue?

Thanks in advance

 Comments   
Comment by Lawrin Novitsky [ 2019-01-29 ]

Thank you for your report.
Are you absolutely sure that our installer is to blame here? Sounds a bit unbelievable...
What are versions of the workbench and the ODBC connector, that we could repeat the issue with?

Comment by IT Particip [ 2019-01-29 ]

Hi Lawrin,

I went from MariaDB ODBC Driver 3.0.7 to 3.0.8 and the Workbench I have is 8.0.14. Same issue appeared on the computer of my boss.

My Workbench was working yesterday and stopped working after upgrading the connector. I am not sure that your installer is to blame, because now that I think about it, we do have a software distribution system which could be causing the issue. In fact I see some lines of code there which aim at removing any existing MySQL ODBC drivers, which is what we were using before migrating to the MariaDB ODBC driver. This, as stupid as it may sound, may be triggering the uninstall process of the Workbench. The Oracle guys created a while ago a centralized installer/uninstaller for all MySQL software pieces, which sometimes produces some undesired behaviour like this.

You may test it anyway if you want, to be sure the installer is working fine, but I do think the problem is on our side.

Thanks for your time!

Comment by Lawrin Novitsky [ 2019-01-30 ]

Let's do this - I am closing the ticket so far, as I think we have good reasons to think it's not the issue on our side. If find out some new facts, proving our installer's guilt - please re-open the ticket. And if you find problems with our connector - please to not hesitate to report it here. This is always welcome.

Generated at Thu Feb 08 03:27:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.