I would think that cross-version mysqldump is not expected to work, but unfortunately the documentation not only doesn't support this claim, but implies otherwise by having "mysqldump and old versions of MySQL" section. Of course the use case described there is different, it's about dumping the current schema and loading it somewhere else; but still, if we start documenting incompatibilities as special cases, it means that everything is compatible otherwise, and if it's not, it must be mentioned in the documentation as well.

serg, what do you think? Do we want to support the backward compatibility of clients with older servers, or document that we don't?

I would suggest to implement a check around the "SHOW PACKAGES" command, which is a 10.3 thing, so it is not fired when server doesn't support it, or at least do not error out on it.

I guess some customers may find 10.3 client installed by default on many linux distros soon,
and their databases will still be 10.1 or 10.2...

I think it's a bug

Hi I couldn't reproduce this error.
The steps that I did:
1) Run 10.2 server
2) Create table,procedure in database called `dbdump`
3) Dump database [with the flags from MDEV] `dbdump` in file `dbdump.sql`
4) Run 10.3 server
5) Insert data from file `dbdump.sql` in a database `test`
6) Dump database `test` [with the flags from MDEV]
Right ?

Try to dump a database 10.2 with mysqldump 10.3, it fails.
The import is unimportant, the issue is dumping it.

Well, another month has gone by. Perhaps a different scenario might help communicate that this is a problem that needs a solution sooner rather than later.

1) Run 10.2 Server or less on a remote server. Perhaps a web host somewhere.
2) Have 10.3 installed on your workstation (perhaps you are a web developer working for clients on all kinds of hosts, and 10.3 is just what comes with your distribution).
3) From your workstation, run mysqldump, giving the proper connection information for the server machine.
4) The dump will fail.

If you do not have shell access to the remote server (it is not uncommon for web hosts to disallow this access), the most practical approach is to install the Oracle version of the software, just for interoperability. It is easier to do this with your distribution's package manager than to downgrade.

Hi Alan, thanks, will try to do that.
I have tried dumping file (10.3) to remote (10.2) and this works

mysql -u user <10.3_file.sql 

Using mysqldump from 10.3 do this:

mysqldump -u user -h 10.2-host schema_from_10.2_server >> 10.2_file.sql

It will fail.

Please, please, please, try to reproduce the problem as stated. Please do not substitute versions.

I ran into the same issue. This is a very annoying, ie. on Arch Linux, where you have to build older versions, which takes hours.

And especially when taking this into account

mysqldump from an earlier MariaDB release cannot be used on MariaDB 10.3 and beyond.

from https://mariadb.com/kb/en/library/mysqldump/

We need some kind of --flag to be able to use mysqldump from Maria 10.3 with older versions.

[addon] Works without --routines (for me)

Closed with 620f4f8af98666e2

Nice and thanks to share it with us.

–
Thanks & Regards
WebHostingReviewsX