Bug #7339 restore doesn't work
Submitted: 16 Dec 2004 1:52 Modified: 16 Dec 2004 16:03
Reporter: Mark Junker Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Administrator Severity:S1 (Critical)
Version:1.0.17 OS:Windows (WinXP SP2)
Assigned to: CPU Architecture:Any

[16 Dec 2004 1:52] Mark Junker
Description:
Hi,

I cannot restore backups created with MySQL Administrator. It shows the progress dialog but the restore doesn't progress.

Regards,
Mark

How to repeat:
Here is a backup file that shows the error:

-- MySQL-Administrator dump 1.3
--
-- ------------------------------------------------------
-- Server version	4.1.7-nt

SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT;
SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS;
SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION;
SET NAMES utf8;

/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!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 */;

CREATE DATABASE /*!32312 IF NOT EXISTS*/ `test`;
USE `test`;
CREATE TABLE `test1` (
  `test1_id` int(10) unsigned NOT NULL auto_increment,
  `test2` text NOT NULL,
  `test3` int(10) unsigned NOT NULL default '0',
  `test2_id` int(10) unsigned NOT NULL default '0',
  PRIMARY KEY  (`test1_id`),
  KEY `FK_test1_1` (`test2_id`),
  CONSTRAINT `FK_test1_1` FOREIGN KEY (`test2_id`) REFERENCES `test2` (`test2_id`) ON DELETE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
CREATE TABLE `test2` (
  `test2_id` int(10) unsigned NOT NULL auto_increment,
  `data` text NOT NULL,
  PRIMARY KEY  (`test2_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
CREATE TABLE `test3` (
  `test3_id` int(10) unsigned NOT NULL auto_increment,
  `text` text NOT NULL,
  PRIMARY KEY  (`test3_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;
/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT;
SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS;
SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION;
/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
[16 Dec 2004 15:35] Jerome Canler
I had exactly the same problem during restore process : progress stayed at 0%

I solved this by changing the file charset from utf8 to latin1.

So I think there's a problem in the charset auto detection as it tells 'probably
utf8'
[16 Dec 2004 16:03] MySQL Verification Team
Duplicate for #7208