Hey everyone, we apologize for the current unexpected downtime.
We have had a long-standing issue where certain data could not be stored properly. For example, Git allows users to have both a main and a MAIN branch (different casing), but Codeberg could not store it, because our database was case-insensitive.
We have been preparing and testing a fix (which is currently converting the database tables). However, we missed that certain operations would fail during the migration.
…
@Codeberg
I believe you are using MySQL for your back end, and if so, you can set the entire database or entire tables to use case sensitive utf8.
IIRC you can use an ALTER statement to alter an existing database or table make it case sensitive
@nikatjef That's what we did, but the operation took 5 to 10 minutes on some tables.
However, some queries where failing when they compared or joined across tables with different collation while the conversion was ongoing.