Bug #63802 File - Execute SQL File of dump file does not execute in Workbench 5.2.36
Submitted: 19 Dec 2011 19:37 Modified: 30 Dec 2011 15:25
Reporter: Daniel Hofer Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S2 (Serious)
Version:5.2.36 OS:Microsoft Windows (64bit (Win7 or Vista))
Assigned to: CPU Architecture:Any
Tags: Execute SQL File

[19 Dec 2011 19:37] Daniel Hofer
Description:
I've been using mysql-installer-5.5.15.0.msi version of MySQL & Workbench
I'm developing a MySQL database on a 64 bit WIN 7 pc and moving to a 64 bit Vista pc every few days. The dump file is about 80mb.

I upgraded to mysql-workbench-gpl-5.2.36-win32.msi from 5.2.34. Now the dump will not execute with File - Execute SQL File...  Nothing happens, no error msg. Since the file is too big for an sql window, I have to break up the dump file into pieces big enought to fit in memory to execute. Then I'm ok.

I upgraded to mysql-installer-5.5.19.0.msi which also has Workbench 5.2.34. The dump sql file still fails to execute. No error msg.

Size of sql dump file is not the issue, the 1 table file below also doesn't execute whether or not the schema already exists.

How to repeat:
Try this sql file.

CREATE DATABASE  IF NOT EXISTS `test2` /*!40100 DEFAULT CHARACTER SET utf8 */;
USE `test2`;
-- MySQL dump 10.13  Distrib 5.5.15, for Win64 (x86)
--
-- Host: localhost    Database: hdbmysql
-- ------------------------------------------------------
-- Server version	5.5.15

/*!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 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!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' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

--
-- Table structure for table `lookupidnums`
--

DROP TABLE IF EXISTS `lookupidnums`;
/*!40101 SET @saved_cs_client     = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `lookupidnums` (
  `LOGID` int(11) NOT NULL,
  `CLIENTID` int(11) DEFAULT NULL,
  `CONTACTID` int(11) DEFAULT NULL,
  `SALESID` int(11) DEFAULT NULL,
  `BIDNO` int(11) DEFAULT NULL,
  `ORDERNO` int(11) DEFAULT NULL,
  `PROJID` int(11) DEFAULT NULL,
  `JOBNO2D` int(11) DEFAULT NULL,
  `JOBNO3D` int(11) DEFAULT NULL,
  `JOBNOGSCAN` int(11) DEFAULT NULL,
  `JOBNODATAM` int(11) DEFAULT NULL,
  `JOBNOMEDIA` int(11) DEFAULT NULL,
  `JOBNONES` int(11) DEFAULT NULL,
  `JOBNODEPTH` int(11) DEFAULT NULL,
  `INVNO2D` int(11) DEFAULT NULL,
  `INVNO3D` int(11) DEFAULT NULL,
  `INVNOGSCAN` int(11) DEFAULT NULL,
  `INVNODATAM` int(11) DEFAULT NULL,
  `INVNOMEDIA` int(11) DEFAULT NULL,
  `INVNONES` int(11) DEFAULT NULL,
  `INVNODEPTH` int(11) DEFAULT NULL,
  `TRANSMITNO` int(11) DEFAULT NULL,
  `TAPENO` int(11) DEFAULT NULL,
  `MOUPDATE` int(11) DEFAULT NULL,
  PRIMARY KEY (`LOGID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
/*!40101 SET character_set_client = @saved_cs_client */;

--
-- Dumping data for table `lookupidnums`
--

LOCK TABLES `lookupidnums` WRITE;
/*!40000 ALTER TABLE `lookupidnums` DISABLE KEYS */;
INSERT INTO `lookupidnums` VALUES (973,3975,10860,93070,31120108,31120156,3112156,31122070,31127000,31123263,31126000,31128000,31125000,31129000,12110231,11110706,12110359,1110600,1110800,12110540,11110103,31120237,822,12);
/*!40000 ALTER TABLE `lookupidnums` ENABLE KEYS */;
UNLOCK TABLES;
[19 Dec 2011 19:45] Miguel Solorzano
Please try 5.2.36 release. Thanks.
[19 Dec 2011 20:34] Daniel Hofer
Sorry, I mis-typed the Synopsis line. It works in Workbench 5.2.34. It doesn't work in 5.2.36.
[20 Dec 2011 16:13] Armando Lopez Valencia
Thanks a lot for your report
[30 Dec 2011 15:25] Daniel Hofer
Corrected Workbench version # that doesn't work to 5.2.36 in the Synopsis

Additional Problem: Manage Import / Export; Data Import/Restore; Import from Disk; Import from Self-Contained File of a Dump sql file never shows any progress in the Import is running... status bar. I've waited for 5 minutes with no action. Doing the same dump file in 3 separate pieces[80mb takes more memory than is available do run as 1 piece] in a SQL Editor pane take about 30 seconds.