Bug #98205 "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME
Submitted: 13 Jan 2020 14:36 Modified: 21 Jan 2020 10:58
Reporter: Andy Millers Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.19 OS:Windows
Assigned to: CPU Architecture:Any

[13 Jan 2020 14:36] Andy Millers
Description:
hello when i try to reverse Engineer SQL script i have this error 

ERROR: (1, 20) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (8, 20) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (14, 19) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (14, 20) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (23, 29) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (23, 13) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (37, 23) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (48, 41) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (48, 11) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (56, 33) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (56, 8) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (62, 34) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...
ERROR: (62, 20) "*" is not valid at this position, expecting BIT, BOOL, BOOLEAN, DATETIME, DATE, ENUM, ...

How to repeat:
creat sql.sql with this code

DROP TABLE IF EXISTS contenu ;
CREATE TABLE contenu (ID_CONTENU INT AUTO_INCREMENT NOT NULL,
LIB_CONTENU VARCHAR(50),
ICONE_CONTENUE VARCHAR(50),
utilisateur_id_user **NOT FOUND**,
PRIMARY KEY (ID_CONTENU)) ENGINE=InnoDB;

DROP TABLE IF EXISTS type_contenu ;
CREATE TABLE type_contenu (ID_TYPE_CONTENU INT AUTO_INCREMENT NOT NULL,
LIB_TYPE_CONTENU VARCHAR(50),
utilisateur_id_user **NOT FOUND**,
PRIMARY KEY (ID_TYPE_CONTENU)) ENGINE=InnoDB;

DROP TABLE IF EXISTS post ;
CREATE TABLE post (ID_POST INT AUTO_INCREMENT NOT NULL,
LIB_POST VARCHAR(50),
SLUG_POST TEXT,
DATE_POST DATE,
contenu_id_contenu **NOT FOUND**,
utilisateur_id_user **NOT FOUND**,
PRIMARY KEY (ID_POST)) ENGINE=InnoDB;

DROP TABLE IF EXISTS champs ;
CREATE TABLE champs (ID_CHAMPS INT AUTO_INCREMENT NOT NULL,
LIB_CHAMPS VARCHAR(50),
type_contenu_id_type_contenu **NOT FOUND**,
post_id_post **NOT FOUND**,
PRIMARY KEY (ID_CHAMPS)) ENGINE=InnoDB;

DROP TABLE IF EXISTS type_utilisateur ;
CREATE TABLE type_utilisateur (
    ID_TU INT AUTO_INCREMENT NOT NULL,
    LIB_TU VARCHAR(50),
    PRIMARY KEY (ID_TU)
)  ENGINE=INNODB;

DROP TABLE IF EXISTS utilisateur ;
CREATE TABLE utilisateur (ID_USER INT AUTO_INCREMENT NOT NULL,
NOM VARCHAR(50),
PRENOM VARCHAR(50),
NBR_EFNT INT,
PERMIS_B BOOLEAN,
LOGIN TINYTEXT,
MDP VARCHAR(50),
type_utilisateur_id_tu **NOT FOUND**,
PRIMARY KEY (ID_USER)) ENGINE=InnoDB;

DROP TABLE IF EXISTS se_compose ;
CREATE TABLE se_compose (ID_TYPE_CONTENU **NOT FOUND** AUTO_INCREMENT NOT NULL,
ID_CONTENU **NOT FOUND** NOT NULL,
NOM_CHAMPS VARCHAR(50),
ORDRE INT,
PRIMARY KEY (ID_TYPE_CONTENU,
 ID_CONTENU)) ENGINE=InnoDB;

DROP TABLE IF EXISTS a_droit ;
CREATE TABLE a_droit (ID_CONTENU **NOT FOUND** AUTO_INCREMENT NOT NULL,
ID_USER **NOT FOUND** NOT NULL,
PRIMARY KEY (ID_CONTENU,
 ID_USER)) ENGINE=InnoDB;

DROP TABLE IF EXISTS correlation ;
CREATE TABLE correlation (ID_POST **NOT FOUND** AUTO_INCREMENT NOT NULL,
ID_POST_correlation **NOT FOUND**,
PRIMARY KEY (ID_POST)) ENGINE=InnoDB;

ALTER TABLE contenu ADD CONSTRAINT FK_contenu_utilisateur_id_user FOREIGN KEY (utilisateur_id_user) REFERENCES utilisateur (ID_USER);

ALTER TABLE type_contenu ADD CONSTRAINT FK_type_contenu_utilisateur_id_user FOREIGN KEY (utilisateur_id_user) REFERENCES utilisateur (ID_USER);
ALTER TABLE post ADD CONSTRAINT FK_post_contenu_id_contenu FOREIGN KEY (contenu_id_contenu) REFERENCES contenu (ID_CONTENU);
ALTER TABLE post ADD CONSTRAINT FK_post_utilisateur_id_user FOREIGN KEY (utilisateur_id_user) REFERENCES utilisateur (ID_USER);
ALTER TABLE champs ADD CONSTRAINT FK_champs_type_contenu_id_type_contenu FOREIGN KEY (type_contenu_id_type_contenu) REFERENCES type_contenu (ID_TYPE_CONTENU);
ALTER TABLE champs ADD CONSTRAINT FK_champs_post_id_post FOREIGN KEY (post_id_post) REFERENCES post (ID_POST);
ALTER TABLE utilisateur ADD CONSTRAINT FK_utilisateur_type_utilisateur_id_tu FOREIGN KEY (type_utilisateur_id_tu) REFERENCES type_utilisateur (ID_TU);
ALTER TABLE se_compose ADD CONSTRAINT FK_se_compose_ID_TYPE_CONTENU FOREIGN KEY (ID_TYPE_CONTENU) REFERENCES type_contenu (ID_TYPE_CONTENU);
ALTER TABLE se_compose ADD CONSTRAINT FK_se_compose_ID_CONTENU FOREIGN KEY (ID_CONTENU) REFERENCES contenu (ID_CONTENU);
ALTER TABLE a_droit ADD CONSTRAINT FK_a_droit_ID_CONTENU FOREIGN KEY (ID_CONTENU) REFERENCES contenu (ID_CONTENU);
ALTER TABLE a_droit ADD CONSTRAINT FK_a_droit_ID_USER FOREIGN KEY (ID_USER) REFERENCES utilisateur (ID_USER);
[21 Jan 2020 10:58] MySQL Verification Team
Hello Andy Millers,

Thank you for the report.
I tried to reproduce your issue on windows 10 with workbench 8.0.19.
IMHO you are using wrong SQL statement, i.e I was getting same error even when I try to run the statements in CLI.

Regards,
Ashwini Patil