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.

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

[DOCS]: Suggest using utf8mb4_bin for collation #28627

Closed
wants to merge 1 commit into from
Closed

[DOCS]: Suggest using utf8mb4_bin for collation #28627

wants to merge 1 commit into from

Commits on Dec 28, 2023

  1. [DOCS]: Suggest using utf8mb4_bin for collation

    For MySQL, suggest using `utf8mb4_bin` for collation, rather than
    `utf8mb4_general_ci`, because the latter is case insensitive, and can
    break assumptions in various parts of Gitea. Such as branch names:
    branch names are case sensitive in git, but with a case insensitive
    collation, and the branch names stored in the database, repositories
    with branch names that differ in case only can lead to internal errors.
    
    This little change updates the documentation only, as a first step of
    addressing the problem.
    
    Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
    algernon committed Dec 28, 2023
    Configuration menu
    Copy the full SHA
    8e3691b View commit details
    Browse the repository at this point in the history