Double byte languages (Japanese) in db get mangled on import
-
I fix it by copy/pasting this from the beginning of a Sequel Pro dump:
/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE=’NO_AUTO_VALUE_ON_ZERO’ */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;https://www.ads-software.com/plugins/all-in-one-wp-migration/
Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
- The topic ‘Double byte languages (Japanese) in db get mangled on import’ is closed to new replies.