Executing (default): SHOW INDEX FROM `users`

[smidhunraj]

when i run node server.js

of this following code here https://github.com/bezkoder/node-js-jwt-auth

I get the following output

(node:20977) [SEQUELIZE0004] DeprecationWarning: A boolean value was passed to options.operatorsAliases. This is a no-op with v5 and should be removed. (Use node --trace-deprecation ... to show where the warning was created) Server is running on port 8080. Executing (default): CREATE TABLE IF NOT EXISTS users (id INTEGER NOT NULL auto_increment , username VARCHAR(255), email VARCHAR(255), password VARCHAR(255), createdAt DATETIME NOT NULL, updatedAt DATETIME NOT NULL, PRIMARY KEY (id)) ENGINE=InnoDB;

Executing (default): SHOW INDEX FROM users Executing (default): CREATE TABLE IF NOT EXISTS roles (id INTEGER , name VARCHAR(255), createdAt DATETIME NOT NULL, updatedAt DATETIME NOT NULL, PRIMARY KEY (id)) ENGINE=InnoDB; Executing (default): SHOW INDEX FROM roles Executing (default): CREATE TABLE IF NOT EXISTS user_roles (createdAt DATETIME NOT NULL, updatedAt DATETIME NOT NULL, roleId INTEGER , userId INTEGER , PRIMARY KEY (roleId, userId), FOREIGN KEY (roleId) REFERENCES roles (id) ON DELETE CASCADE ON UPDATE CASCADE, FOREIGN KEY (userId) REFERENCES users (id) ON DELETE CASCADE ON UPDATE CASCADE) ENGINE=InnoDB; Executing (default): SHOW INDEX FROM user_roles

[meghead]

Same issue here. Seems it's just a warning. https://stackoverflow.com/questions/58593200/deprecationwarning-a-boolean-value-was-passed-to-options-operatorsaliases-this

[Kingyungu]

@smidhunraj did you find a solution to the problem? I'm having the same issues.

[michaelniemand]

@smidhunraj did you find a solution to the problem? I'm having the same issues.

it's not an error. The script just ends this way. See: https://stackoverflow.com/a/69078907

Same issue here. Seems it's just a warning. https://stackoverflow.com/questions/58593200/deprecationwarning-a-boolean-value-was-passed-to-options-operatorsaliases-this

it's in fact just a warning; the 'SHOW INDEX FROM users' issue is unrelated and not actually an issue