MySQL database dump with --force option still stops on errors

[maxiride]

Description

When executing a dump task of multiple databases and specifying the --force option in the extra commands field, the database dump process dumps databases one by one. When an error occurs, the dump of the current databases proceeds as expected with the --force option, but dbeaver does not proceed to dump the next database and stops.

The expected behaviour would be to proceed dumping the rest of the selected databases, it's like if mysql correctly applies the --force option but then DBeaver seeing an error in the log stops not "acknowledging" that the error was intentionally ignored.

DBeaver Version

Community 23.3.0.202312ecc

Operating System

Windows 10

Database and driver

Database MySQL 8
Driver: default from DBeaver wizard

Steps to reproduce

1. Right click a database and select Tools -> Dump database
   
2. Select multiple databases
   
3. Specify the --force option
   
4. Observe that databases are dumped in alphabetical order, when a table\view with an error arise the error is logged and the current database dump completes.
5. DBeaver stops processing the dump task of the remaining databases. The expected behaviour would be to proceed.

Additional context

No response

[E1izabeth]

Thank you for bug report. I reproduces the issue on db1 (MariaDB) with Elizabeth database.