Preview feature feedback: `extendedIndexes`
See original GitHub issuePlease share your feedback about the extendedIndexes
preview feature released in v3.5.0 in this issue.
- If you encounter a bug, please open a bug report in this repo.
- If the feature is working well for you, please share this in a comment below or leave a 👍 on this issue.
If you have any questions, don’t hesitate to ask them in the #product-feedback channel in the Prisma Slack.
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Prisma Client and Prisma schema preview features
When we release a new Prisma Client or Prisma schema feature, it often starts in preview so that you can test it and...
Read more >How to configure indexes in Prisma - LogRocket Blog
Configuring indexes in Prisma. From Prisma version 3.5.0 and above, indexes can be enabled through the extendedIndexes preview feature. But, ...
Read more >Prisma 3.14.0 Release - GitClear
We introduced the extendedIndexes Preview feature in version 3.5.0 , and we have been adding new configuration options for indexes.
Read more >Prisma 4.0 Released: The Next Gen ORM - Morioh
Here's a TL;DR: Preview features moved to General Availability. extendedIndexes; filterJson; improvedQueryRaw. Improvements to the Prisma Schema.
Read more >Prisma-whats-new - Linen
preview feature in your Prisma Schema: generator client { provider = "prisma-client-js" previewFeatures = ["namedConstraints"] } When using prisma db pull
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This exactly the bug we’re having right now as well. It just drops and recreates all indexes, including unique indexes, for every migration.
Saw this locally last night as well. Adding
extendedIndexes
and thenmigrate
resulted in the index being dropped and recreated. Aside from that, it seemed to work as intended.