[TYPO3] [Typo3] Indexed Search (CVS Version) + MySQL 4.1 + UTF-8 => no results with special chars

Dmitry Dulepov typo3 at fm-world.ru
Mon Feb 13 13:14:00 CET 2006


Nikolas Hagelstein wrote:
> Dimitry, so what do you think about 
> setting DB fields encoding to utf8  and
> force DB collation(connection) to utf8 
> (by adding a "set names utf8" to tslib).
> Having db and collation in latin1 could 
> get you into trouble when doing sql dump
> import/export without an appropriate --default-charset during
> export.

I use mysql 3.23, it does not have utf-8 at all. Locale is set to
latin1. I do backups daily and restore them to develoipment server from
time to time. No problems with non-ascii characters.

I remember discussion about database charset, it was set that it must be
latin1 to avoid problems. I do not remember anything else because it did
not intetest me much. But you can search if you need this information.

> Trouble occurs if the db connection is set to something
> else than the enconding of the DB field. This will result
> in charset conversion (done by mysql) which will lead to 
> broken chars.

It does not. At least, in my installations.

> Imho it would be a good idea to improve the typo3 DB layer
> to have nativ utf8 support on demand.

And break compatibility with older mysqls...

"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)

More information about the TYPO3-english mailing list