diff options
| author | wxiaoguang <wxiaoguang@gmail.com> | 2024-01-10 19:03:23 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-10 11:03:23 +0000 |
| commit | 2df7563f3176aa8c7dcb070f660d53da4bb66e78 (patch) | |
| tree | acf64c3f4d40f15e0fc28d4f6060644172cc46f0 /options | |
| parent | a80debc208fbf0ecf6ca734e454cae08adafb570 (diff) | |
| download | gitea-2df7563f3176aa8c7dcb070f660d53da4bb66e78.tar.gz gitea-2df7563f3176aa8c7dcb070f660d53da4bb66e78.zip | |
Recommend/convert to use case-sensitive collation for MySQL/MSSQL (#28662)
Mainly for MySQL/MSSQL.
It is important for Gitea to use case-sensitive database charset
collation. If the database is using a case-insensitive collation, Gitea
will show startup error/warning messages, and show the errors/warnings
on the admin panel's Self-Check page.
Make `gitea doctor convert` work for MySQL to convert the collations of
database & tables & columns.
* Fix #28131
## :warning: BREAKING :warning:
It is not quite breaking, but it's highly recommended to convert the
database&table&column to a consistent and case-sensitive collation.
Diffstat (limited to 'options')
| -rw-r--r-- | options/locale/locale_en-US.ini | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/options/locale/locale_en-US.ini b/options/locale/locale_en-US.ini index 3c564f518e..0e5d91bd57 100644 --- a/options/locale/locale_en-US.ini +++ b/options/locale/locale_en-US.ini @@ -2691,6 +2691,7 @@ teams.invite.description = Please click the button below to join the team. [admin] dashboard = Dashboard +self_check = Self Check identity_access = Identity & Access users = User Accounts organizations = Organizations @@ -3216,6 +3217,13 @@ notices.desc = Description notices.op = Op. notices.delete_success = The system notices have been deleted. +self_check.no_problem_found = No problem found yet. +self_check.database_collation_mismatch = Expect database to use collation: %s +self_check.database_collation_case_insensitive = Database is using a collation %s, which is an insensitive collation. Although Gitea could work with it, there might be some rare cases which don't work as expected. +self_check.database_inconsistent_collation_columns = Database is using collation %s, but these columns are using mismatched collations. It might cause some unexpected problems. +self_check.database_fix_mysql = For MySQL/MariaDB users, you could use the "gitea doctor convert" command to fix the collation problems, or you could also fix the problem by "ALTER ... COLLATE ..." SQLs manually. +self_check.database_fix_mssql = For MSSQL users, you could only fix the problem by "ALTER ... COLLATE ..." SQLs manually at the moment. + [action] create_repo = created repository <a href="%s">%s</a> rename_repo = renamed repository from <code>%[1]s</code> to <a href="%[2]s">%[3]s</a> |