Bug #108858 Selected tables not used after restarting data import in Workbench
Submitted: 24 Oct 2022 2:43 Modified: 18 Nov 2022 2:37
Reporter: Stefano Young Email Updates:
Status: Not a Bug Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.22 OS:MacOS (10.15.4)
Assigned to: CPU Architecture:Any

[24 Oct 2022 2:43] Stefano Young
When restarting a data import (Dump Data Only) after stopping in the middle, the import starts from the first table instead of using the selected tables indicated by the Import checkboxes.

How to repeat:
Import from a Dump Project Folder.

Select schema objects to import.

Start Import, then stop before it completes.

Return to the "Import from Disk" tab and start import again.

View the log to see that import starts from the first table instead of the first selected table.

Suggested fix:
Continue to use the selected tables after a data import is stopped in the middle.
[17 Nov 2022 12:52] MySQL Verification Team
Hello Stefano Young,

Thank you for the bug report.
Imho, this is by design and not a bug. If you can provide more information, feel free to add it to this bug.
Thank you for your interest in MySQL.

Ashwini Patil
[18 Nov 2022 2:37] Stefano Young
The key point is, when you return to the "Import from Disk" tab after stopping an import, the table selections are still shown in the UI. But if you import again, the next import starts from the first table in alphabetical order, *not* the first table you selected. I don't have screenshots but maybe this will help:

1. Select tables 2 and 3
[ ] table1
[x] table2
[x] table3

2. Start import (import starts from table2)

3. Stop import before it finishes

4. Return to "Import from Disk" tab. It still shows the selections
[ ] table1
[x] table2
[x] table3

5. Start import again

6. This time, import starts from table1 instead of table2 (BUG). Import should start from table2 like before.