Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

SequelizeMeta structure incompatible with SingleStore/memsql

Open
#1,397 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, sql
Domain
cli, databases

Research direction

Start at the SequelizeMeta table initialization that emits the shown CREATE TABLE statement and trace how its name column constraints are assembled for the memsql/SingleStore dialect. Verify the generated schema against the reported SingleStore error; done means SequelizeMeta initializes without the duplicate UNIQUE constraint while preserving the primary key behavior.

Written by the indexing model from the issue text.

Description

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:

CREATE TABLE IF 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

CREATE TABLE IF 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.

Dialect: memsql/SingleStore
Database version: 8.1
Sequelize CLI version: 5.5.1
Sequelize version: 6.17.0

Dominant language
JavaScript
Stars
2.6k
Forks
524
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sequelize/cli

All issues in sequelize/cli

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.