… SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET…
Comment: Best kept MySQLDump Secret
March 29, 2012 By 11 Comments
… SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `z` ( `n` char(1) DEFAULT ” ) ENGINE=InnoDB DEFAULT CHARSET=utf8; /*!40101 SET character_set… (‘a’); /*!40000 ALTER TABLE `z` ENABLE KEYS */; UNLOCK TABLES; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; …
Comment: Fixing column encoding mess in MySQL
March 14, 2012 By 32 Comments
Before banging head to the table after “ALTER TABLE CONVERT TO CHARACTER SET utf8″ try looking at your columns via HEX(column_name).. It did convert everything very well. My problem was not setting connection encoding… i.e. “SET NAMES utf8″ ..
Comment: Fixing column encoding mess in MySQL
March 14, 2012 By 32 Comments
…. MyISAM tables with latin1 encoding. Tried: ALTER TABLE CONVERT TO CHARACTER SET utf8; Does nothing except changes table/column encodings, but no… try the nr2 way mentioned in this blog: UPDATE table SET column=CONVERT(CONVERT(column USING binary) USING utf8) WHERE id…
Post: Converting Character Sets
March 17, 2009 By 16 Comments
… a database (or set of tables) to a target character set and collation. Approach #1: ALTER TABLE `t1` CONVERT TO CHARACTER SET utf8 COLLATE utf8… CHARSET=utf8, MODIFY COLUMN `c1` text CHARACTER SET utf8; This approach will both change the default character set for the table and target column…
Post: Ultimate MySQL variable and status reference list
January 8, 2011 By 4 Comments
….commanual character_set_clientblogpercona.commanual character_set_client_handshakeblogpercona.commanual character_set_connectionblogpercona.commanual character_set_databaseblogpercona.commanual character_set_filesystemblogpercona.commanual character_set_resultsblogpercona.commanual character_set…
Post: Using CHAR keys for joins, how much is the overhead ?
June 18, 2007 By 18 Comments
… i and j columns to varchar while sticking to utf8 character set which we had as default ? Joining on Char columns completes… this setting does not work any more. The next test I decided to do is to convert Innodb table to latin1 character set… for this test was – latin1 encoding is enough for most character based keys – uuid, sha1/md5 based etc. Latin1 encoding indeed…
Comment: Why MySQL could be slow with large tables ?
March 12, 2007 By 139 Comments
…_increment, `STRING` varchar(100) character set utf8 collate utf8_unicode_ci NOT NULL default ”, `URL` varchar(230) character set utf8 collate utf8_unicode_ci…) NOT NULL, `TITLE` varchar(255) character set utf8 collate utf8_unicode_ci NOT NULL default ”, `DESCRIPTION` text character set utf8 collate utf8_unicode_ci…
Post: Innodb row size limitation
April 7, 2011 By 11 Comments
… trailer)/2. For the default page size of 16kb. this sets an ~8000 bytes limit on row size (8126 as reported… values, not the character-size. This means if you insert a 500 character string with all multi-byte characters into a VARCHAR(500… you hit this error after converting from a native language character set to utf8, as it can increase the size dramatically. If…
Comment: 7 Reasons why MySQL Quality will never be the same
December 11, 2008 By 15 Comments
… features in MySQL 4.1 were Subselects, Prepared Statements and Character Sets. All they were not done by Monty and these were… their good share of bugs with repeated execution etc. Finally character sets required changes across all parts of the server and also… in the cases when you mix collations and use different character sets in the application. It took a good time before 4…
