asked on
Using mysql to backup database - weird characters in the dump file
I am using mysqldump. When I open up the dump file that it created using notepad, parts of the file look like this:
Uë*O\0Š‡ã=ãúw{r€bÊð½|0ë÷(2
Most of the file is in readable English, though. What's the deal with this? Is this normal? Will the import work without a problem?
Here is my command:
mysqldump --opt --user root --password=1q2w3e4r wikidb > sql.dump
Uë*O\0Š‡ã=ãúw{r€bÊð½|0ë÷(2
Most of the file is in readable English, though. What's the deal with this? Is this normal? Will the import work without a problem?
Here is my command:
mysqldump --opt --user root --password=1q2w3e4r wikidb > sql.dump
MySQL Server
Last Comment
Nem Schlecht
I hope that isn't your actual root password.
ASKER
It is not my actual root password.
Yes, this should dump/load properly - as long as you don't muck with the 'sql.dump' file (opening it in any editor and then saving would be bad).
You did a good job of posting a cryptic root password! ;-)
You must have a BLOB() field or maybe a TEXT() field that contains some binary data of some sort. Is this a common thing in your database (every 10th row looks like garbage) or is there only 1 or two entries that look like this?
You must have a BLOB() field or maybe a TEXT() field that contains some binary data of some sort. Is this a common thing in your database (every 10th row looks like garbage) or is there only 1 or two entries that look like this?
ASKER
I looked in the dump file and there is actually only one section that has the weird characters. The section begins right after this code:
--
-- Dumping data for table `wzobjectcache`
--
LOCK TABLES `wzobjectcache` WRITE;
/*!40000 ALTER TABLE `wzobjectcache` DISABLE KEYS */;
INSERT INTO `wzobjectcache` VALUES ('wikidb-wz:messages:en','
--
-- Dumping data for table `wzobjectcache`
--
LOCK TABLES `wzobjectcache` WRITE;
/*!40000 ALTER TABLE `wzobjectcache` DISABLE KEYS */;
INSERT INTO `wzobjectcache` VALUES ('wikidb-wz:messages:en','
What's the CREATE statement for table 'wzobjectcache' look like?
You can either get it from the dump or via:
SHOW CREATE TABLE wzobjectcache;
You can either get it from the dump or via:
SHOW CREATE TABLE wzobjectcache;
ASKER
--
-- Table structure for table `wzobjectcache`
--
DROP TABLE IF EXISTS `wzobjectcache`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `wzobjectcache` (
`keyname` varbinary(255) NOT NULL DEFAULT '',
`value` mediumblob,
`exptime` datetime DEFAULT NULL,
PRIMARY KEY (`keyname`),
KEY `exptime` (`exptime`)
) ENGINE=InnoDB DEFAULT CHARSET=binary;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wzobjectcache`
--
LOCK TABLES `wzobjectcache` WRITE;
/*!40000 ALTER TABLE `wzobjectcache` DISABLE KEYS */;
INSERT INTO `wzobjectcache` VALUES ('wikidb-wz:messages:en','
áóͼ(¾øåãÿ ','2038-01-19 03:14:07');
/*!40000 ALTER TABLE `wzobjectcache` ENABLE KEYS */;
UNLOCK TABLES;
-- Table structure for table `wzobjectcache`
--
DROP TABLE IF EXISTS `wzobjectcache`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `wzobjectcache` (
`keyname` varbinary(255) NOT NULL DEFAULT '',
`value` mediumblob,
`exptime` datetime DEFAULT NULL,
PRIMARY KEY (`keyname`),
KEY `exptime` (`exptime`)
) ENGINE=InnoDB DEFAULT CHARSET=binary;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Dumping data for table `wzobjectcache`
--
LOCK TABLES `wzobjectcache` WRITE;
/*!40000 ALTER TABLE `wzobjectcache` DISABLE KEYS */;
INSERT INTO `wzobjectcache` VALUES ('wikidb-wz:messages:en','
áóͼ(¾øåãÿ ','2038-01-19 03:14:07');
/*!40000 ALTER TABLE `wzobjectcache` ENABLE KEYS */;
UNLOCK TABLES;
ASKER
It is a Mediawiki database that I am backing up, if that makes a difference. And it very small in size, under 2MB.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
So when I do the import, it should be fine, right?
Yup, you should be okay.
Let me double-check, though. If you're using phpMyAdmin, you may have problems. It does *not* use the standard mysqldump format (its very close, but slightly different). I would use the 'mysqldump' and 'mysql' commands to make sure the dump/load will work correctly.
Let me double-check, though. If you're using phpMyAdmin, you may have problems. It does *not* use the standard mysqldump format (its very close, but slightly different). I would use the 'mysqldump' and 'mysql' commands to make sure the dump/load will work correctly.