Bug #110442 Import SQL Script on ERR Diagram Crashs Workbench

• Submitted: 20 Mar 2023 20:23
• Modified: 24 Mar 2023 10:39
• Reporter: Natã Pereira
• Status: Can't repeat
• Category: MySQL Workbench: Modeling
• Severity: S2 (Serious)
• Version: 8.0.32
• OS: Windows (Microsoft Windows 11)
• CPU Architecture: Any
• Tags: WBBugReporter

[20 Mar 2023 20:23] Natã Pereira

Description:
When importing a SQL Script to create tables in ERR Diagram, the app crashes if there are any 'CHECK' statements in the SQL Script.

I was trying to import a script that had the following table creation:
CREATE TABLE customer (
    id INT AUTO_INCREMENT PRIMARY KEY,
    name VARCHAR(255) NOT NULL,
    contract_type ENUM('msp', 'reseller', 'partner') NOT NULL,
    tier TINYINT NOT NULL CHECK (tier >= 1 AND tier <= 4),
    type ENUM('enterprise', 'comercial', 'internal') NOT NULL
);

Every time I tried importing it, Workbench would just crash.

By removing the CHECK in the 'tier' column, it worked:
CREATE TABLE customer (
    id INT AUTO_INCREMENT PRIMARY KEY,
    name VARCHAR(255) NOT NULL,
    contract_type ENUM('msp', 'reseller', 'partner') NOT NULL,
    tier TINYINT NOT NULL CHECK (tier >= 1 AND tier <= 4),
    type ENUM('enterprise', 'comercial', 'internal') NOT NULL
);

How to repeat:
Create a new model and try to import a SQL Script for reverse engineer, with the content in the description above and the crash will happen.

[24 Mar 2023 10:39] MySQL Verification Team

Hello Natã Pereira,

Thank you for the bug report.
I tried to reproduce your issue on windows 10 with workbench 8.0.32 using table provided but I am not seeing any issues at my end.

Regards,
Ashwini Patil