Bug #94179 export table record as sql insert statements didn`t write table name
Submitted: 2 Feb 2019 17:28 Modified: 4 Feb 2019 6:22
Reporter: mohamed atef Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:8.0.14, 8.0.15, 8.0.16, 8.0.26 OS:Windows
Assigned to: CPU Architecture:Any
Tags: export table record as sql insert statements didn`t write table name

[2 Feb 2019 17:28] mohamed atef 
Description:
when exporting table record as sql insert statement
it will export table name as emoty string ~~

How to repeat:
create database db;
use db;
CREATE TABLE `tb1` (
  `ID` bigint(20) unsigned NOT NULL,
  `DT` varchar(50) COLLATE utf8_unicode_ci NOT NULL,
  PRIMARY KEY (`ID`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;

insert into db.tb1 (ID,DT) VALUES (1,'A');
SELECT * FROM db.tb1;
1 ROW RETURNED

WHEN EXPORT IT AS SQL INSERT STATEMENT
AND CONFIRM TABLE NAME IN THE TABLE NAME SHOWING DIALOG FORM

THE RESULT WILL BE 

/*
-- Query: SELECT * FROM db.tb1
-- Date: 2019-02-02 20:27
*/
INSERT INTO `` (`ID`,`DT` ) VALUES (1,'A');

Suggested fix:
ENSURE THAT TABLE NAME IS WRITTEN IN THE EXPORTED RECORDS
[4 Feb 2019 6:22] MySQL Verification Team 
Hello Mohamed,

Thank you for the report and feedback.
Verified as described.

thanks,
Umesh
[9 Feb 2019 5:42] MySQL Verification Team 
Bug #94254 marked as duplicate of this one
[2 Mar 6:09] MySQL Verification Team 
Bug #106613 marked as duplicate of this one
[5 May 23:26] Liu Tong 
Is this scheduled to fix? I was impacted by this for around 2 years. Super inconvenient to export data.