 |
By (user no longer on site)
over a year ago
|
This is quite simple to achieve in principle. The character set encoding used by the database needs to be utf8mb4. Actually implementing that change requires the database engine having support for the encoding. There is always a risk of database corruption during the conversation, but that's what backing up is for...
Any competent sysadmin would be able to complete the conversion in their sleep. However the current implementation is a "value added perk" for subscribers, enabling it for everyone would be counterproductive to the bank balance  |
Reply privately, Reply in forum +quote
or View forums list | |
» Add a new message to this topic
