I hope you don't mean the part about deprecating the existing the use of "SLAVE", that's really not acceptable.

It's one thing that some people dislike some word, and a lot of extra code is added to the server. But it's very disrespectful to try to force such dislike on other people and make them spend extra effort to change their setup or handle deprecation warnings.

Does this idea of deprecating the use of "slave" in replication code come from somewhere?

- Kristian.

knielsen, the most of the abolishment 'slave' aliasing has been done in MDEV-20601. So this one has to follow suit already via a consistency argument.

> Does this idea of deprecating the use of "slave" in replication code come from somewhere?
Yes, from there. It's all rooted by MDEV-18777. I love some of the users' comments!
But there's no actual plan to deprecate, thankfully! (Sorry for confusing you in the original version of this reply, I had not caught up on the development of 18777 discussion).

I wish I could rewind to that discussion to suggest as an alternative e.g a enterprise connector feature to re-write queries for supposedly historical justice minded DBA:s.

Hey Elkin!

This is ready for review: PR 2760

reminder ^

Looks good. Sorry for delaying this very small one.

danblack: thanks for the heads up! Small ones like this should be automatically listed on the top of one's sprint list items. Oth, of course 'smallness' can't be always termed in the line number . This time it could.