You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The table schema for the SequelizeMeta table is in conflict with the memsql/SingleStore dbms. The problematic query is the following table create:
CREATETABLEIF NOT EXISTS `SequelizeMeta` (`name`VARCHAR(255) NOT NULL UNIQUE , PRIMARY KEY (`name`));
which causes an error due to validation on the memsql side with name being the PK and also defined as UNIQUE explicitly
SQL Error [1706] [HY000]: Feature 'Multiple HASH indices on the same columns' is not supported by
SingleStore.
simply skipping the explicit UNIQUE constraint on name avoids this issue
CREATETABLEIF NOT EXISTS `SequelizeMeta` (`name`VARCHAR(255) NOT NULL , PRIMARY KEY (`name`));
Is there any reason not to remove the unique flag in the table definition? It is theoretically extraneous since it is the PK already.
What do you expect to happen?
I would expect the SequelizeMeta table to initialize successfully without intervention - or for there to be a way to configure my way out of the problem.
What is actually happening?
Error is being thrown due to validation on the dbms being confused that the key is also manually defined as unique.
SQL Error [1706] [HY000]: Feature 'Multiple HASH indices on the same columns' is not supported by
SingleStore.
What you are doing?
The table schema for the SequelizeMeta table is in conflict with the memsql/SingleStore dbms. The problematic query is the following table create:
which causes an error due to validation on the memsql side with
name
being the PK and also defined as UNIQUE explicitlysimply skipping the explicit
UNIQUE
constraint onname
avoids this issueIs there any reason not to remove the unique flag in the table definition? It is theoretically extraneous since it is the PK already.
What do you expect to happen?
I would expect the SequelizeMeta table to initialize successfully without intervention - or for there to be a way to configure my way out of the problem.
What is actually happening?
Error is being thrown due to validation on the dbms being confused that the key is also manually defined as unique.
Dialect: memsql/SingleStore
Database version: 8.1
Sequelize CLI version: 5.5.1
Sequelize version: 6.17.0
The text was updated successfully, but these errors were encountered: