Thread:Project:Support desk/UTF8 Problem with update from 1.16 to 1.17/reply (10)

> If I understand correctly you shouldn't let the table latin1 encoded. Yes.

> So in our case it's necessary to turn the table page back to binary or UTF-8.

Basically you are right: Your tables should either be set to be UTF-8 encoded or binary. But be careful: You must make sure that, when you switch your tables to UTF-8 (or to binary), you in fact have UTF-8-encoded data in them. You generally can store data, which has any encoding, in a DB table with any - possibly other - encoding. If you did that, you would run into strange problems, e.g. as described at the beginning of this thread.