Add FAQ for case sensitivity problem with MySQL #6127
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nabenabe0928
reviewed
Jun 6, 2025
| @@ -775,3 +775,32 @@ However, if it is necessary to remove artifacts from a Python script, users can | |||
| for artifact_meta in get_all_artifact_meta(study): | |||
| # Remove the artifacts uploaded to ``base_path``. | |||
| artifact_store.remove(artifact_meta.artifact_id) | |||
|
|
|||
| How can I resolve case sensitivity issues with MySQL? | |||
| ------------------------------------------------------ | |||
There was a problem hiding this comment.
Suggested change
| ------------------------------------------------------ | |
| ----------------------------------------------------- |
Comment on lines
+783
to
+784
| However, Optuna treats string parameters in a case-sensitive manner. | ||
| This can lead to conflicts when parameter names differ only by case. |
There was a problem hiding this comment.
Suggested change
| However, Optuna treats string parameters in a case-sensitive manner. | |
| This can lead to conflicts when parameter names differ only by case. | |
| However, Optuna treats string parameters in a case-sensitive manner, leading to conflicts in MySQL if parameter names differ only by case. |
| A = trial.suggest_int("A", 0, 10) | ||
| return a + A | ||
|
|
||
| In this case, "a" and "A" are treated as distinct by Optuna, but MySQL considers them the same due to its default collation settings. |
There was a problem hiding this comment.
Suggested change
| In this case, "a" and "A" are treated as distinct by Optuna, but MySQL considers them the same due to its default collation settings. | |
| In this case, Optuna treats `a` and `A` distinctively while MySQL does not due to its default collation settings. |
| return a + A | ||
|
|
||
| In this case, "a" and "A" are treated as distinct by Optuna, but MySQL considers them the same due to its default collation settings. | ||
| As a result, an error may occur when trying to register these parameters in the database. |
There was a problem hiding this comment.
Suggested change
| As a result, an error may occur when trying to register these parameters in the database. | |
| As a result, only one of the parameters will be registered in MySQL. |
| In this case, "a" and "A" are treated as distinct by Optuna, but MySQL considers them the same due to its default collation settings. | ||
| As a result, an error may occur when trying to register these parameters in the database. | ||
|
|
||
| To address this issue, there are some workarounds. |
There was a problem hiding this comment.
Suggested change
| To address this issue, there are some workarounds. | |
| The following workarounds should be considered: |
| 1. Use a different storage backend. | ||
| Please consider using PostgreSQL or SQLite, which supports case-sensitive handling. | ||
| 2. Rename the parameters to avoid case conflicts. | ||
| For example, use "a" and "b" instead of "a" and "A". |
There was a problem hiding this comment.
Suggested change
| For example, use "a" and "b" instead of "a" and "A". | |
| For example, use `a` and `b` instead of `a` and `A`. |
| For example, use "a" and "b" instead of "a" and "A". | ||
| 3. Change MySQL’s collation settings to be case-sensitive. | ||
| You can configure case sensitivity at the database, table, or column level. | ||
| For more details, refer to `the MySQL documentation <https://dev.mysql.com/doc/refman/9.3/en/charset-syntax.html>`__. |
There was a problem hiding this comment.
Suggested change
| For more details, refer to `the MySQL documentation <https://dev.mysql.com/doc/refman/9.3/en/charset-syntax.html>`__. | |
| We defer to `the MySQL documentation <https://dev.mysql.com/doc/refman/9.3/en/charset-syntax.html>`__ for more details. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
An error with MySQL was report in #6032.
Following an internal discussion, we decided to add a description of the issue and its possible workarounds to the FAQ.
Description of the changes
The output is like:
