rubyforgood / rubyforgood/casa
Ensure indexes present
Open
Nobody has claimed this yet.
📈 Performance Improvement
no-issue-activity
- Dominant language
- Ruby
- Stars
- 381
- Forks
- 542
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 47
Description
Since there was some concern mentioned this weekend (at the RfG Event 2025) lets do a pass to ensure that indexes are present in the database and creatd them if not.
- any column that ends in
_id - any FK column
- any other column that is joined on
- columns that are commonly used in WHERE clauses
If no action is needed that would be fine, and it closes this issue.
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
No files or tests are named. Start by reviewing the database schema and checking the listed foreign-key, *_id, joined, and commonly filtered columns for existing indexes; done means the relevant indexes are present or the review confirms that no action is needed.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100