Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Warning "Option column_case_sensitive is not provided" during MySQL user setup #535

Open
tisba opened this issue Jan 3, 2024 · 4 comments · May be fixed by #557
Open

Warning "Option column_case_sensitive is not provided" during MySQL user setup #535

tisba opened this issue Jan 3, 2024 · 4 comments · May be fixed by #557
Labels
stale

Comments

@tisba
Copy link

tisba commented Jan 3, 2024 •
edited
Loading

I'm on 4.3.4 and just saw this warning:

[…]
TASK [geerlingguy.mysql : Ensure MySQL users are present.] ********************************************************************************************************************************************************************
ok: [myhost.example.com] => (item={'name': 'app', 'host': 'localhost', 'password': 'geheim', 'priv': {'app.*': 'ALL'}})
[WARNING]: Option column_case_sensitive is not provided. The default is now false, so the column's name will be uppercased. The default will be changed to true in community.mysql 4.0.0.
[…]

edit: I guess this originates from https://github.com/geerlingguy/ansible-role-mysql/blob/master/tasks/users.yml. Since the default of column_case_sensitive will change, maybe this needs to become configurable?
@iamyacin iamyacin mentioned this issue Mar 6, 2024
Closed
@github-actions GitHub Actions
Copy link

github-actions bot commented May 4, 2024

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@github-actions github-actions bot added the stale label May 4, 2024
@tisba
Copy link
Author

tisba commented May 6, 2024

This issue is still relevant IMO.

@github-actions github-actions bot removed the stale label May 11, 2024
@tolecnal
Copy link

I'm just referring back to @tisba comment from May 6th, this issue is still quite relevant. I used this role on numerous occasions over the last few months, and seeing this warning is unnecessary given it should be fairly easy to fix in the code.

You can of course argue that the warning is quite trivial, and not relevant to most users, but warnings are warnings and most people would want to avoid them if at all possible.

@github-actions GitHub Actions
Copy link

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@github-actions github-actions bot added the stale label Dec 14, 2024
tolecnal added a commit to tolecnal/ansible-role-mysql that referenced this issue Dec 15, 2024
@tolecnal
Introducing the column_case_sensitive for the users task.
934e3fb 
This fixes the warning message: "Option column_case_sensitive is not provided. The default is now false, so the column's name will be uppercased. The default will be changed to true in community.mysql 4.0.0.".

Resolves geerlingguy#535
@tolecnal tolecnal linked a pull request Dec 16, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Introducing the column_case_sensitive for the users task. tolecnal/ansible-role-mysql
2 participants
@tisba @tolecnal