| Bug #102948 | Migration - Table Objects Select Bug | ||
|---|---|---|---|
| Submitted: | 12 Mar 2021 9:37 | Modified: | 12 Mar 2021 10:50 |
| Reporter: | Tomáš Hůla | Email Updates: | |
| Status: | Won't Fix | Impact on me: | |
| Category: | MySQL Workbench: Migration | Severity: | S2 (Serious) |
| Version: | 8.0.23 | OS: | Windows |
| Assigned to: | CPU Architecture: | x86 | |
| Tags: | migrate migration bug tables select selection ui | ||
[12 Mar 2021 9:37]
Tomáš Hůla
[12 Mar 2021 10:50]
MySQL Verification Team
Hello Tomáš Hůla, Thank you for the report and feedback. Verified as described on Win10. regards, Umesh
[14 Feb 2024 11:56]
Michael Beaton
Note that some viable work-arounds for this issue are included in this MySQL Forums thread: https://forums.mysql.com/read.php?152,695267
[11 Dec 2024 17:51]
Yoni Sade
God, it has been more than three years since this bug was open. Could you please finally fix it for god's sake? (and other Workbench ancient bugs for that matter)
[21 Nov 2025 11:29]
Marko Todoric
Year 2025 (almost 2026) and this bug is still here.
[3 May 4:58]
fei wang
Solution: 1) Click "Show Selection" 2) Click the "<<" in the middle 3) Use the wildcard at the top, such as entering *user* to select the "users" table and then click ">>" 4) Continue the same method to select other tables Then "next" can be used to migrate individual tables at this point
[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.
