Bug #92417 '' set as default value for INT type column when migrating

• Submitted: 14 Sep 2018 7:32
• Modified: 14 Oct 2018 8:43
• Reporter: Michał Więckowski
• Status: No Feedback
• Category: MySQL Workbench: Migration
• Severity: S3 (Non-critical)
• Version: 8.0.12
• OS: Any
• CPU Architecture: Any

[14 Sep 2018 7:32] Michał Więckowski

Description:
Migrate data between SQL Server 2017 and MySQL is giving a wrong default value for INT comlumns. When the script for new tables generation is completed I can find that there are many places where INT is set to default value of '', for example:

CREATE TABLE IF NOT EXISTS `myname`.`Table1` (
  `version` INT NOT NULL DEFAULT '',
...
)

And this, of course, is not working in next steps of migration process (Invalid default value for 'version'). 

How to repeat:
Try to migrate SQL Server 2017 database to MySQL 8 with ODBC(native). 

Suggested fix:
Default values should be set accordingly to column type.

[14 Sep 2018 8:43] MySQL Verification Team

Thank you for the bug report. Please provide an example sql create statement for SQL server to test for migration it. Thanks.

[21 Sep 2018 13:28] Milosz Bodzek

Hey Michał, can you please provide source table SQL to help us reproduce issue? Thanks in advance.

[15 Oct 2018 1:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".