mirror of
https://github.com/ansible-collections/community.mysql.git
synced 2025-04-05 10:10:32 -07:00
033b4c74f9
* Add integrations tests for column case sensitive name * add a warning when column_case_sensitive in not set * add announce default will change in in 4.0.0 * fix tests for engine that don't wrap column in backticks * add filter because only MySQL 5.7 is case sensitive for users privs * add kmarse and myself to the authors * add kmarse to the contributors list --------- Co-authored-by: Laurent Indermühle <laurent.indermuehle@epfl.ch> Co-authored-by: Andrew Klychkov <aklychko@redhat.com>
21 lines
1.1 KiB
YAML
21 lines
1.1 KiB
YAML
---
|
|
minor_changes:
|
|
|
|
- mysql_user - add ``column_case_sensitive`` option to prevent field names
|
|
from being uppercased
|
|
(https://github.com/ansible-collections/community.mysql/pull/569).
|
|
- mysql_role - add ``column_case_sensitive`` option to prevent field names
|
|
from being uppercased
|
|
(https://github.com/ansible-collections/community.mysql/pull/569).
|
|
|
|
major_changes:
|
|
- mysql_user - the ``column_case_sensitive`` argument's default value will be
|
|
changed to ``true`` in community.mysql 4.0.0. If your playbook expected the
|
|
column to be automatically uppercased for your users privileges, you should
|
|
set this to false explicitly
|
|
(https://github.com/ansible-collections/community.mysql/issues/577).
|
|
- mysql_role - the ``column_case_sensitive`` argument's default value will be
|
|
changed to ``true`` in community.mysql 4.0.0. If your playbook expected the
|
|
column to be automatically uppercased for your roles privileges, you should
|
|
set this to false explicitly
|
|
(https://github.com/ansible-collections/community.mysql/issues/578).
|