Bug #85349 LONG column type translated to MEDIUMTEXT
Submitted: 7 Mar 2017 19:49 Modified: 7 Mar 2017 23:41
Reporter: Javier Ortiz Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.3.6 OS:Ubuntu
Assigned to: CPU Architecture:Any

[7 Mar 2017 19:49] Javier Ortiz
Description:
The LONG column type is translated to MEDIUMTEXT when doing migration, copy SQL to clipboard.

How to repeat:
1. Select table ExecuteStep in the attached Workbench project.
2. Copy SQL for the table and inspect the column execution_time.
[7 Mar 2017 19:50] Javier Ortiz
Filse showing the issue.

Attachment: Validation Master.mwb (application/vnd.mysql-workbench-model, text), 146.83 KiB.

[7 Mar 2017 23:41] MySQL Verification Team
Thank you for the bug report. That is expected behavior:

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 5
Server version: 5.7.19 Source distribution PULL: 2017-MAR-07

Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql 5.7 > use test
Database changed
mysql 5.7 > create table x (id long);
Query OK, 0 rows affected (0,32 sec)

mysql 5.7 > show create table x;
+-------+-----------------------------------------------------------------------------+
| Table | Create Table                                                                |
+-------+-----------------------------------------------------------------------------+
| x     | CREATE TABLE `x` (
  `id` mediumtext
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
+-------+-----------------------------------------------------------------------------+
1 row in set (0,00 sec)

mysql 5.7 > 

https://dev.mysql.com/doc/refman/5.7/en/other-vendor-data-types.html