You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the docs really should mention that the tables will be created with the servers default collation (perhaps we should be specifying collation on table creation), it does mention the characterset but doesnt mention collation.
For example, MariaDB default collation is latin1_swedish_ci, and this will cause a load of issues with ombi pertaining to special characters, switching to utf8mb4_unicode_ci resolves it of course
The text was updated successfully, but these errors were encountered:
There's a note about charset in the docs, but the migration script was written by someone else - not us.
I'll look into putting some better notation in place.
I think the docs really should mention that the tables will be created with the servers default collation (perhaps we should be specifying collation on table creation), it does mention the characterset but doesnt mention collation.
For example, MariaDB default collation is latin1_swedish_ci, and this will cause a load of issues with ombi pertaining to special characters, switching to utf8mb4_unicode_ci resolves it of course
The text was updated successfully, but these errors were encountered: