Update mysql_db.py, adding encoding to enforce charset for import

[netmonk]

SUMMARY

encoding is used for creation of database, but not for import of sql scripts.
The import fails to import latin1 encoded sql script, cause it consider it's by default some utf8

This commit add --default-character-set=encoding when the import function is called with an encoding argument.
This way this option is added to the mysql command line, and import is successfull.

ISSUE TYPE

• Bugfix Pull Request
• Docs Pull Request
• Feature Pull Request
• New Module Pull Request

COMPONENT NAME

mysql_db

ADDITIONAL INFORMATION

[ansibot]

cc @Alexander198961 @Andersson007 @Xyon @bmalynovytch @bmildren @kurtdavis @michaelcoburn @Oneiroi @tolland
click here for bot help

[ansibot]

The test ansible-test sanity --test pep8 [explain] failed with 1 error:

lib/ansible/modules/database/mysql/mysql_db.py:182:161: E501 line too long (165 > 160 characters)

click here for bot help

[abadger]

Hi, two things:

• Changes should be submitted to the devel branch and then backported after merging. That way we don't reintroduce a bug when we release new versions
• 2.7 is only open for critical bugfixes right now. This is probably not going to meet the definition of a critical bugfix (it doesn't affect the core engine. It doesn't prevent any use of the mysql_db module. etc). However, 2.8 and 2.9 (in development) are still accepting non-critical bugfixes so this can be backported to those once it is in the devel branch.

Could you please reopen this against devel?

[netmonk]

Hello @abadger i understand your point.
I already have another PR opened for upstream #61215 in the same time than this one.
I wanted to backport in 2.7 as far as i use RHEL7 and they only distribute ansible 2.7 on LTS package.

If you can have a look at the PR on devel branch i submitted, would be nice too :)