Problem

Each of the available mysqldump export formats possesses a significant problem:

The fact that there is no good solution to this problem is, at least in my view, a reason to avoid MySQL or MariaDB wherever possible, until the problem is fixed.

I view it as a major issue, because there is no workaround available: with MySQL/MariaDB, you have no choice but to compromise one of those important factors, and if that is not viable, then an alternative product must be used. However, others may disagree, so I have reported it as a "minor" issue. Please modify that to "major" if you agree that this warrants it.

Proposed solution

As described here by Kendall Bennett, `mysqldump --extended-insert` should be fixed to format its output the same way as MySQL Administrator used to.

I.e. when fixed, mysqldump --extended-insert would yield this:

INSERT INTO `coupon_gv_customer` (`customer_id`,`amount`) VALUES 

 (887,'0.0000'),

 (191607,'1.0300');

instead of this:

INSERT INTO `coupon_gv_customer` (`customer_id`,`amount`) VALUES (887,'0.0000'),191607,'1.0300');

According to Tim Riker and Lon Binder the fix is as simple as this:

On line 3506, you can see where the row-ending comma is output:
fputc(',',md_result_file); /* Always row break */

Simply insert this line immediately after line 3506:
fputc('\n',md_result_file); /* Lon Binder says wrap that line! */

If Riker and Binder are correct that the fix is that trivial, then I hope the MariaDB devs/maintainers will be able to easily and quickly patch and backport it into the versions of mysqldump that they ship.

Thank you for your work on MariaDB!