Tracking Issue - Database table, column, index, and foreign keys are too long

[derrickmehaffy]

Bug report

Describe the bug

This is a tracking issue for the various issues regarding lengths in the database being too long:

• Error: ER_TOO_LONG_IDENT: Identifier name - Foreign Keys:
  • foreign key index names too long for mariadb (MySQL has same limits) #12339
  • Foreign Key Constraint Too Long on MySQL #13014
• error: create index - Index Names:
  • Index names are not handled gracefully when they are too long #13031
• Error: ER_TOO_LONG_IDENT: Identifier name - Components
  • Error: ER_TOO_LONG_IDENT | Too long column names hit character restriction in database #12101
  • Long component names are not reflected in database #13116

We need to handle length constraints more gracefully across the entire database layer, maybe utilize short-codes like comp, ect.

Steps to reproduce the behavior

See various linked issues

Expected behavior

Each database should have properly length controlled tables, columns, indexes, and foreign keys

Additional context

Additional duplicate issues will be linked in the comments below:

[derrickmehaffy]

#10636
#9199

https://forum.strapi.io/t/create-index-already-exists/16835/2

[strapi-bot]

This issue has been mentioned on Strapi Community Forum. There might be relevant details there:

https://forum.strapi.io/t/strapi-v4-postgres-render-com-error-knex-timeout-acquiring-a-connection-the-pool-is-probably-full-are-you-missing-a-transacting-trx-call/16506/5