Home  >  Q&A  >  body text

SQL syntax error 1064: There is an incorrect "VISIBLE" part in your SQL syntax

I'm actually just trying and experimenting with MySQL Workbench and Azure Database for the first time. So, I modeled a simple model on MySQL Workbench and when I try to sync with azure database, I get the following error.

MySQL Workbench 8.0 Azure MySQL version: 5.7

RROR: Error 1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'VISIBLE,
  PRIMARY KEY (`emp_id`),
  UNIQUE INDEX `employee_id_UNIQUE` (`emp_id`' at line 20
SQL Code:
        CREATE TABLE IF NOT EXISTS `azcare_schema`.`employee` (
          `id` INT(11) NOT NULL AUTO_INCREMENT,
          `emp_id` VARCHAR(10) NOT NULL,
          `first_name` VARCHAR(20) NULL DEFAULT NULL,
          `middle_name` VARCHAR(30) NULL DEFAULT NULL,
          `last_name` VARCHAR(20) NULL DEFAULT NULL,
          `date_of_birth` VARCHAR(45) NULL DEFAULT NULL,
          `gender` CHAR(6) NULL DEFAULT NULL,
          `marital_status` VARCHAR(20) NULL DEFAULT NULL,
          `nationality` VARCHAR(30) NULL DEFAULT NULL,
          `passport_number` VARCHAR(20) NULL DEFAULT NULL,
          `sponser` VARCHAR(40) NULL DEFAULT NULL,
          `joining_date` DATE NULL DEFAULT NULL,
          `department` CHAR(100) NULL DEFAULT NULL,
          `education_degree` VARCHAR(45) NULL DEFAULT NULL,
          `religion` VARCHAR(30) NULL DEFAULT NULL,
          `blood_group` CHAR(4) NULL DEFAULT NULL,
          `create_time` TIMESTAMP NULL DEFAULT CURRENT_TIMESTAMP,
          `update_time` TIMESTAMP NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
          UNIQUE INDEX `id_UNIQUE` (`id` ASC) VISIBLE,
          PRIMARY KEY (`emp_id`),
          UNIQUE INDEX `employee_id_UNIQUE` (`emp_id` ASC) VISIBLE)
        ENGINE = InnoDB
        DEFAULT CHARACTER SET = utf8

SQL script execution finished: statements: 3 succeeded, 1 failed

Fetching back view definitions in final form.
Nothing to fetch

P粉742550377P粉742550377183 days ago347

reply all(1)I'll reply

  • P粉937769356

    P粉9377693562024-04-01 17:36:17

    Based on @ErgestBasha's suggestion. VISIBLE Introduced on MySQL 8.0 Azure MySQL version is 5.7

    I fixed the error by updating MySQL Workbench Preference-> MYSQL -> Default Target MySQL Version to 5.7

    reply
    0
  • Cancelreply