CSBans/PGBans storage: двойное кодирование имён и причин в MySQL — соединение не задаёт charset
This issue describes a double-encoding problem in MySQL storage for CSBans/PGBans when handling player names with Cyrillic characters. The MySQL connection is not explicitly setting its character set, leading to UTF-8 encoded data being misinterpreted as latin1 (cp1252) and then re-encoded, resulting in corrupted data visible to external tools. The proposed fix is to explicitly set the connection charset to 'utf8' after creating the database tuple.