May 23, 2012

Post: Best kept MySQLDump Secret

… = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `C` ( `t` char(255) NOT NULL, `i` int(11) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1; /*!40101 SET character_set

Comment: Best kept MySQLDump Secret

…`; /*!40101 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_client… (‘a’); /*!40000 ALTER TABLE `z` ENABLE KEYS */; UNLOCK TABLES; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; …

Post: Converting Character Sets

… way of utf8.  Drizzle has chosen it as the default character set, most back-ends to websites use it to store text… -> ) ENGINE=MyISAM DEFAULT CHARSET=latin1; Query OK, 0 rows affected (0.02 sec) mysql> ALTER TABLE `t1` CONVERT TO CHARACTER SET utf8 COLLATE…: ALTER TABLE `t1` DEFAULT CHARSET=utf8, MODIFY COLUMN `c1` text CHARACTER SET utf8; This approach will both change the default character set for the table and…

Comment: MySQL File System Fragmentation Benchmarks

… my tests: computer 1: My.ini [client] port=3306 [mysql] default-character-set=latin1 [mysqld] port=3306 basedir=”C:/Program Files/MySQL/MySQL…:/Program Files/MySQL/MySQL Server 5.0/Data/” default-character-set=latin1 default-storage-engine=INNODB #default-storage-engine=MyISAM sql-mode=”STRICT_TRANS_TABLES…

Comment: When is it a time to upgrade memory ?

…” into the config file. The “innodb_buffer_pool_size” is set to 4Go but the whole database size is almost 8Go…=30 wait_timeout=15 max_allowed_packet=64M default-collation=utf8_unicode_ci default-character-set=utf8 default-storage-engine=InnoDB bulk_insert_buffer_size…_concurrency=2 innodb_file_per_table=1 innodb_doublewrite=0 # Set buffer pool size to 50-80% of your computer’s…

Post: MySQL Installation and upgrade scripts.

… could screw your data, for example by specifying utf8 as default character set together not to mention infamous timestamp format change which forced… tested at all. For example if you use RHEL4 in default configuration (which is having SELinux enabled) upgrading RedHat RPM to…

Post: Ultimate MySQL variable and status reference list

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

Comment: Why MySQL could be slow with large tables ?

…` varchar(100) character set utf8 collate utf8_unicode_ci NOT NULL default ”, `URL` varchar(230) character set utf8 collate utf8_unicode_ci NOT NULL default ”, `LANGUAGE… NULL default ‘EN’, `COUNTRY` char(2) NOT NULL, `TITLE` varchar(255) character set utf8 collate utf8_unicode_ci NOT NULL default ”, `DESCRIPTION` text character set utf8…

Comment: Multiple column index vs multiple indexes

…` varchar(100) character set utf8 NOT NULL, `address` varchar(50) character set utf8 default NULL, `city` varchar(30) character set utf8 default NULL, `state` varchar(2) default NULL, `zip` int(5) unsigned NOT NULL, `country` varchar(20) default

Post: Using CHAR keys for joins, how much is the overhead ?

… j columns to varchar while sticking to utf8 character set which we had as default ? Joining on Char columns completes in 4.5… 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…