For non-transactional engine, there should be an option that binary logs are written just after updating row. If binary logs are written only when the statement is finished, it generally means that non-transactional engine has to use table locks to ensure correct replication, like MyISAM.

also there's absolutely no reason why the MySQL identifier "utf8" should remain limited to 3-byte sequences, unless you really want to say that MySQL is not Unicode compliant (the fact that the charset is registered in IANA as "UTF-8" with a minus-hyphen that is not

Plane 1 (incresing number of symbols in modern use) and plane 2 (ideographic supplement, needed for GB18030 compliance for products in China) is becoming more urgently needed. Please cover the whole Unicode encoding space, make MySQL fully Unicode-compliant, add the missing 16 planes and

SELECT * FROM utf8_table WHERE CONVERT( utf8_column USING latin1 ) COLLATE latin1_german2_ci = _latin1 'Aerger'

Support collation by a certain locale ( sorting order of characters)

This bug is important to MediaWiki, the software used by Wikipedia. MediaWiki supports full Unicode but does not use MySQL's Unicode support because it does not support full Unicode.

MediaWiki has an important long-standing bug regarding correct collation for its many languages which

high, nice addition to euckr, does it suppor Hebrew yet, or can I start working on the project? Regards Como seducir a una mujer

woow good

One can always work on something else, more important and so, but there are key features MySQL lacks and this is definitely one of them...

Very good idea. I have some suggestions:

* Maybe it would be possible to convert DATE, DATETIME, TIMESTAMP, YEAR? * Maybe it would be possible to convert TIME, DATETIME, TIMESTAMP? * Maybe ENUM and SET could be converted into string types? * Maybe SET could be converted into BIT? (first