Last modified: 2013-11-14 12:22:16 UTC
When using replication on a MediaWiki database, the following warnings show up in the MySQL log when using the Translate extension: [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statement is unsafe because it accesses a non-transactional table after accessing a transactional table within the same transaction. Statement: INSERT /* DatabaseTTMServer::insertSource */ INTO `translate_tmf` (tmf_sid,tmf_text) VALUES ('421','search data') This problem is caused by the fact that the translate_tmf is using the MyISAM storage engine. All MediaWiki tables are using InnoDB except for this translate_tmf and the searchindex table, as InnoDB lacks the FULLTEXT index support. See http://www.mediawiki.org/wiki/Manual_talk:Searchindex_table. Transactions to the translate_tmf table should be separated from other transactions to the database to prevent unsafe statements from happening when using replication.
Hi Maarten. We're not planning on fixing this. If you want a scalable translation memory with the translate extension, please consider using the Solr backend. Patches are welcome and will be reviewed.
Additionally, starting with MySQL 5.6.4, there is support for full text search in InnoDB.
