README.md Developer Notes #12 states: "Database collation: Use utf8mb4_general_ci (not unicode_ci) for new tables." But in migrations/000_baseline.sql, saved_filters (~line 158) and ticket_attachments (~line 188) both use utf8mb4_unicode_ci, inconsistent with every other table in the schema.
Mixed collations on the same charset don't break anything by themselves today, but any future query that joins/compares these columns against general_ci columns will need explicit COLLATE casts or will hit "Illegal mix of collations" errors.
Fix: Add a migration to convert both tables' text columns to utf8mb4_general_ci for consistency with the rest of the schema and the documented convention.
**Severity:** Medium
README.md Developer Notes #12 states: "Database collation: Use `utf8mb4_general_ci` (not `unicode_ci`) for new tables." But in `migrations/000_baseline.sql`, `saved_filters` (~line 158) and `ticket_attachments` (~line 188) both use `utf8mb4_unicode_ci`, inconsistent with every other table in the schema.
Mixed collations on the same charset don't break anything by themselves today, but any future query that joins/compares these columns against `general_ci` columns will need explicit `COLLATE` casts or will hit "Illegal mix of collations" errors.
**Fix:** Add a migration to convert both tables' text columns to `utf8mb4_general_ci` for consistency with the rest of the schema and the documented convention.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Severity: Medium
README.md Developer Notes #12 states: "Database collation: Use
utf8mb4_general_ci(notunicode_ci) for new tables." But inmigrations/000_baseline.sql,saved_filters(~line 158) andticket_attachments(~line 188) both useutf8mb4_unicode_ci, inconsistent with every other table in the schema.Mixed collations on the same charset don't break anything by themselves today, but any future query that joins/compares these columns against
general_cicolumns will need explicitCOLLATEcasts or will hit "Illegal mix of collations" errors.Fix: Add a migration to convert both tables' text columns to
utf8mb4_general_cifor consistency with the rest of the schema and the documented convention.