Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

Specify DB columns to be indexed #104

Closed
marktani opened this issue Feb 16, 2017 · 5 comments
Closed

Specify DB columns to be indexed #104

marktani opened this issue Feb 16, 2017 · 5 comments

Comments

@marktani
Copy link
Contributor

marktani commented Feb 16, 2017

Currently, for a given model, the id field, all unique fields and all relations are indexed already.

@dubiousdavid
Copy link

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.

@marktani
Copy link
Contributor Author

Thanks for the suggestion @dubiousdavid, this is related to #65. 🙂

@marktani
Copy link
Contributor Author

Closing in favor of https://github.com/graphcool/framework/issues/1300. @dubiousdavid would love to hear your feedback on the linked proposal!

@Xample
Copy link

Xample commented Oct 7, 2019

@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)

@ehxxn
Copy link

ehxxn commented Nov 5, 2019

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 🤲

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants