The documentation now suggests adding an init_command in settings to try and fix the persistent load errors on l10n data.
Unfortunately, at least for MySQL 5.0.x on Windows, it doesn't work. Probably not for Unix either.
Possibly a better test would be to actually check it in the satchmo_check management command. Code for mysql would be roughly as follows:
from django.db import connection if connection.connection.class.module == 'MySQLdb.connections': unless connection.connection.character_set_name() = 'utf8': # Report an error! elif ... # postgres.
No clue if the other Python DB APIs have the connection set name in the same place.
Reported by ash