ansible-collections/community.mysql
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.mysql.git synced 2025-07-23 13:20:25 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

sql_mode can be set in session, therefore we should look for ANSI_QUOTES in session variable instead of global variable (#677)

Browse source 
* issue-671: get ASNI_QUOTES from session sql_mode instead of GLOBAL sql_mode
This commit is contained in:
Soledad208 2024-11-07 15:56:31 +07:00 • committed by GitHub
commit ebb37ae7a3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
4 changed files with 131 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

12
changelogs/fragments/671-modules_util_user.yml Normal file
View file

@ -0,0 +1,12 @@
bugfixes:
- mysql_user,mysql_role - The sql_mode ANSI_QUOTES affects how the modules mysql_user
and mysql_role compare the existing privileges with the configured privileges,
as well as decide whether double quotes or backticks should be used in the GRANT
statements. Pointing out in issue 671, the modules mysql_user and mysql_role allow
users to enable/disable ANSI_QUOTES in session variable (within a DB session, the
session variable always overwrites the global one). But due to the issue, the modules
do not check for ANSI_MODE in the session variable, instead, they only check in the
GLOBAL one.That behavior is not only limiting the users' flexibility, but also not
allowing users to explicitly disable ANSI_MODE to work around such bugs like
https://bugs.mysql.com/bug.php?id=115953.
(https://github.com/ansible-collections/community.mysql/issues/671)