Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Composite index name too long

See original GitHub issue

So I was creating a table tonight with 6 fields put into a compound index per the docs.

field: {type:Sequelize.STRING(34), unique:'main'},
another_field: {type:Sequelize.STRING(34), unique:'main'},
a_date_field: {type:Sequelize.STRING(34), unique:'main'},
yet_another_field: {type:Sequelize.STRING(34), unique:'main'},
almost_done_field: {type:Sequelize.STRING(34), unique:'main'},
last_field: {type:Sequelize.STRING(34), unique:'main'}

I’m getting an error from MySQL. ER_TOO_LONG_IDENT “Identifier name is too long”.

Sequelize is combining my field names to create an index name rather than using the ‘main’ string I’m providing.

Is there a way to provide the index name to avoid this issue?

Issue Analytics

State:
Created 9 years ago
Comments:13 (3 by maintainers)

Top GitHub Comments

8reactions

natesilvacommented, Jan 29, 2018

Please reopen this. This is a bug in lib/associations/belongs-to-many.js, injectAttributes().

https://github.com/sequelize/sequelize/blob/f36db54dd5b031427fd8c52296c614c56421e4ba/lib/associations/belongs-to-many.js#L262

This line creates an index name for a BelongsToMany table, and if the name is longer than 64 characters it will fail on MySQL. On PostgreSQL I believe the name will be truncated to 63 chars, which also is not desirable.

Ideally I’d have the option to specify the index name myself.

1reaction

sushantdhimancommented, Jul 27, 2019

uniqueKey name can be overridden now https://github.com/sequelize/sequelize/pull/9914