Re: [midgard-issues] [Issue 103] Sql Interface breaks with UTF-8

[email protected] wrote:

> Can we make MySQL version 4.1.1 or newer a requirement for 1.7.4/1.8? That would
> simplify character set handling quite a lot.

Yes we can , but do we have time to test things?
 
> What needs to be done to fix this:
> 
> 1) Change the troublesome index definitions in datagard.
> 
> 2) Change datagard to set the character set of new databases to UTF-8.
> 
> 3) Add a Midgard configuration setting for specifying the client character set.
> For now the default would be to use the MySQL default if a character set is not
> specified, later on (1.9) this could be changed to UTF-8.
> 
> 4) Add a wiki documentation page about the character encodings and migrating
> databases to UTF-8.
> 
> 5) Mention the changes in the release notes.
> 
> Piotras, is it OK if I change datagard and MidgardConfig accordingly?

Yup, thanks!

Piotras