Files identified in the description:
None

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

@platypus-geek: Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information.

Here are the items we could not find in your description:

• component name

Please set the description of this issue with this template:
https://raw.githubusercontent.com/ansible/ansible/devel/.github/ISSUE_TEMPLATE.md

click here for bot help

Files identified in the description:

• lib/ansible/modules/database/mysql/mysql_db.py

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

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

@pratikgadiya12 Since you recently worked on this feature, can you please comment on this ? Thanks.

+label easyfix

Hi guys. I just want to add one more comment how this change is breaking a lot of deployments.
Currently we are using mysql_db module for dump and import. So we are dumping one database and importing it to another. If the dumped file now has a USE` `db_name`; statement, the import module will ignore the database name and it will import the db to the name in this USE statement. So back to itself.

This doesn't work any more:

- name: Dump the database
  mysql_db:
    state: dump
    name: database1
    login_user: "{{ db_user }}"
    login_host: "{{ db_host }}"
    login_password: "{{ db_pass }}"
    single_transaction: yes
    target: "{{ dump_file }}"

- name: Import the database
  mysql_db:
    state: import
    name: database2
    login_user: "{{ db_user }}"
    login_host: "{{ db_host }}"
    login_password: "{{ db_pass }}"
    target: "{{ dump_file }}"
  register: dbimport_try
  retries: 3
  delay: 5
  until: dbimport_try is not failed

With this bug, import to databse2 will never be executed.
I think the best way would be to revert and not use USE statement in dumps. Otherwise you would have to delete this part from dump somehow before every import. Or use option in the dump module to mitigate this.

Nice regards,
Marko

We encountered the same issue. IMO Ansible should not use --databases unless multiple databases are specified (this is the pre-Ansible-2.9 behavior). Maybe add an option to control the use of --databases. Adding --no-create-db as an option would not fix this as the dump would still contain a USE statement.

This is our workaround for now:

# https://github.com/ansible/ansible/issues/65351
- name: WORKAROUND - Remove "CREATE DATABASE" and "USE" statements from SQL dump
  command: sed -i -e '/^CREATE DATABASE /d' -e '/^USE /d' /tmp/dump.sql