From 1c3f9e5b5a00a9ba976572e736b47c8f28808d9a Mon Sep 17 00:00:00 2001 From: Weston Ruter Date: Thu, 5 Sep 2013 17:05:45 -0700 Subject: [PATCH] Specify DB_CHARSET as default-character-set for wp-db-import A DB export followed by a DB import of the same file was resulting in corrupted UTF-8 characters. The script was being run in the varying-vagrant-vagrants environment which has latin1 as the default charset: mysql> show variables like "character_set_%"; +--------------------------+----------------------------+ | Variable_name | Value | +--------------------------+----------------------------+ | character_set_client | latin1 | | character_set_connection | latin1 | | character_set_database | latin1 | | character_set_filesystem | binary | | character_set_results | latin1 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | /usr/share/mysql/charsets/ | +--------------------------+----------------------------+ --- php/commands/db.php | 1 + 1 file changed, 1 insertion(+) diff --git a/php/commands/db.php b/php/commands/db.php index 0f2be91f..2068248f 100644 --- a/php/commands/db.php +++ b/php/commands/db.php @@ -167,6 +167,7 @@ class DB_Command extends WP_CLI_Command { 'host' => DB_HOST, 'user' => DB_USER, 'pass' => DB_PASSWORD, + 'default-character-set' => DB_CHARSET, ) ); Utils\run_mysql_command( $cmd, $final_args, $descriptors ); -- 2.11.0