Bug #120405 export followed by import fails
Submitted: 5 May 23:30
Reporter: Dave Dyer Email Updates:
Status: Won't Fix Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S7 (Test Cases)
Version:8.0.44 OS:Windows (Microsoft Windows 10 Home)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[5 May 23:30] Dave Dyer
Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\ddyer\AppData\Roaming\MySQL\Workbench\log\wb.log]

the data export/import fails for enum fields which default to null

CREATE TABLE `offlinegame` (
  `owner` int(11) NOT NULL DEFAULT '0',
  `whoseturn` int(11) NOT NULL DEFAULT '0',
  `gameuid` int(11) NOT NULL AUTO_INCREMENT,
  `sequence` int(11) DEFAULT '0',
  `status` enum('setup','active','complete','canceled','suspended') NOT NULL DEFAULT 'setup',
  `marked` enum('delinquent','expired') DEFAULT NULL,
  `offlinegamecol` varchar(45) NOT NULL DEFAULT '0',
  `variation` varchar(30) NOT NULL,
  `playmode` enum('ranked','unranked','tournament') NOT NULL DEFAULT 'ranked',
  `invitedplayers` tinytext,
  `acceptedplayers` tinytext,
  `allowotherplayers` enum('true','false') DEFAULT NULL,
  `body` text,
  `comments` text,
  `created` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `last` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `firstplayer` enum('random','mefirst','youfirst') NOT NULL DEFAULT 'random',
  `speed` enum('day1','day2','day4','day8') NOT NULL DEFAULT 'day2',
  `scored` tinyint(4) NOT NULL DEFAULT '0',
  `chat` text,
  `nag` text,
  `NAGTIME` datetime DEFAULT NULL,
  PRIMARY KEY (`gameuid`),
  KEY `owner` (`owner`),
  KEY `gameuid` (`gameuid`),
  KEY `whoseturn` (`whoseturn`),
  KEY `status` (`status`)
) ENGINE=InnoDB AUTO_INCREMENT=294 DEFAULT CHARSET=latin1;

the field "marked" is exported to csv as "" if the value
is null.   Importing the file results in the fields that should
be null imported as 'delinquent'

How to repeat:

use a table with this structure

Suggested fix:

make it work as intended
[14 Sep 18:07] Omer Barnir
Posted by developer:

This issue applies to the legacy MySQL Workbench 8.x implementation that is no longer supported or maintained.
MySQL Workbench 26.7 is a complete rewrite using a new technology stack and does not use the affected legacy implementation.
Therefore, this issue is not applicable to the current MySQL Workbench product and as such is closed.