This repository has been archived by the owner on Sep 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 867
Specify DB columns to be indexed #104
Comments
A real game changer would be if you could specify multiple columns for an index. In particular, a unique index across more than one field allows you to constrain by, for example, userId and name, so that the name field is unique per user, but not globally unique. |
Thanks for the suggestion @dubiousdavid, this is related to #65. 🙂 |
Closing in favor of https://github.com/graphcool/framework/issues/1300. @dubiousdavid would love to hear your feedback on the linked proposal! |
@mahkali 404 what is the status of this issue ? I am struggling with very poor performances on text search over a set of 2.5m items… (postgres) |
So what if I directly manipulate database and set index on it. I think this will not make any issue for prisma service. I hope 🤲 |
This was referenced Sep 11, 2020
This was referenced Jan 18, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, for a given model, the
id
field, all unique fields and all relations are indexed already.The text was updated successfully, but these errors were encountered: