yesodweb / yesodweb/persistent
Could we add search indexes?
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 486
- Forks
- 306
- PR merge metrics
- No merged PRs in 30d
Description
A client of mine has a bunch of constraints on the table that are simply 'key' (mysql).
I wouldn't know how to model that in a migration, I believe they're just search indexes: https://stackoverflow.com/questions/924265/what-does-the-key-keyword-mean
I think postgress supports this too, by manually creating an index: https://devcenter.heroku.com/articles/postgresql-indexes
And I know mongo does: https://docs.mongodb.com/manual/indexes/
So I'm not asking for a unique constraint, just a way to express an index in the migrations to make queries go faster.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue requests migration support for non-unique search indexes across MySQL, PostgreSQL, and MongoDB backends. No files, tests, or entry points are named; begin by locating the migration APIs and backend-specific migration implementations. Done means indexes can be expressed in migrations without making them unique, with coverage for the affected storage backends.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell, mongodb, mysql, postgresql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100