Bug #114899 MySQL Workbench not compatible with latest MySQL LTS release 8.4.0
| Submitted: | 7 May 2024 2:52 | Modified: | 7 May 2024 5:00 |
|---|---|---|---|
| Reporter: | Abhishek Deshpande | Email Updates: | |
| Status: | Won't Fix | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S2 (Serious) |
| Version: | 8.0.36, 8.0.38 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | MySQL Workbench 8.0.36 | ||
[7 May 2024 2:52]
Abhishek Deshpande
[7 May 2024 5:00]
MySQL Verification Team
Hello Abhishek, Thank you for the report and feedback. regards, Umesh
[25 Jul 2024 8:11]
MySQL Verification Team
Bug #115681 marked as duplicate of this one.
[5 Aug 2024 10:18]
MySQL Verification Team
Bug #115768 marked as duplicate of this one
[24 Jan 2025 22:47]
Wojciech Kapcia
Is there any chance that this could be fixed/released? 8.1 was release 18 months ago. There was a PR to address the issue (https://github.com/mysql/mysql-workbench/pull/45) but it was closed (for legal reasons) While it works some features breaks/are unavailable even though they could work just fineā¦
[14 Sep 18:06]
Omer Barnir
Posted by developer: This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained. MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation. Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.056 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.