[Epic] `extendedIndexes` GA

The feature currently encompasses the sort and length arguments as well as the type argument on Postgres. It was released in 3.5 and 3.6 (type). Main docs here: https://www.prisma.io/docs/concepts/components/prisma-schema/indexes Preview feature feedback can be found here. https://github.com/prisma/prisma/issues/10540

Stabilizing this is a BREAKING CHANGE.

Feature Work

• Fully investigate GiST and GIN index types
  • Then:
    • Support GiST: https://github.com/prisma/prisma/issues/10634
    • Support GIN: https://github.com/prisma/prisma/issues/7410
    • Support BRIN
    • Support SP-GiST
    • https://github.com/prisma/language-tools/issues/1139
• #12818
  • https://github.com/prisma/prisma/issues/13065
• Investigate SQL Server index types
  • SQL Server index clustering settings https://github.com/prisma/prisma/issues/12871
  • https://github.com/prisma/language-tools/issues/1138

Bugs

• recreation of indexes https://github.com/prisma/prisma/issues/11631

Documentation

• https://github.com/prisma/docs/issues/3102
  • https://github.com/prisma/docs/pull/3123

Reference

Use cases

Polishing

• error message to use length on text in mysql https://github.com/prisma/prisma/issues/10292
  • https://github.com/prisma/prisma-engines/pull/2905
• error message incorrect https://github.com/prisma/prisma/issues/10566
  • https://github.com/prisma/prisma-engines/pull/2893

Stabilizing

• Remove extendedIndexes preview feature from datamodel: https://github.com/prisma/prisma/issues/12777
  • https://github.com/prisma/prisma-engines/pull/2907
• Remove extendedIndexes preview feature from docs
• Upgrade guide since this is a breaking change

Issues to close after GA

• https://github.com/prisma/prisma/issues/8661

Out of scope for GA

• add info to dmmf https://github.com/prisma/prisma/issues/3998
• Mysql length limits (discovery document)
  • Mysql length limits config dependent that one needs some more investigation https://github.com/prisma/prisma/issues/10990
  • Mysql length limit validation in schema validation https://github.com/prisma/prisma/issues/10288
• diff and duplicate key error upon second migrate dev run https://github.com/prisma/prisma/issues/10405
• Cyclic creation of the same migration https://github.com/prisma/prisma/issues/12693
• Document: Mysql length limits and db configuration
• Document: Sort order effects in singular vs compound index
• Document: covering indexes (this one is optional)
  • https://github.com/prisma/docs/issues/3131

[pimeys]

GIN/GIST/SP-GiST/BRIN work going on here: https://github.com/prisma/prisma-engines/pull/2858

[sourdzl]

really appreciate this work prisma team! I’ve been having trouble getting prisma to not create migrations dropping a GIN index i tried adding manually to the db, so this feature would really help!