RealDevSquad / RealDevSquad/website-backend
Composite Indexes needed in the Staging Environment for `/progresses`
Open
@prakashchoudhary07 is already working on this.
Since Dec 12, 2023.
- Dominant language
- JavaScript
- Stars
- 74
- Forks
- 276
- Avg merge
- 1d 26m
- Merged PRs (30d)
- 14
Description
Issue Description
Since a new query parameter, date, has been introduced in the /progresses route, we must create new composite indexes in the staging environment. Please note that some indexes may already exist, but to ensure none are overlooked, I have included them below (the indexes after sl no. 4 might be already existing in our indexes):
| Sl No | Collection ID | Fields indexed |
|---|---|---|
| 1 | progresses | taskId Ascending type Ascending date Descending name Descending |
| 2 | progresses | type Ascending date Ascending name Ascending |
| 3 | progresses | taskId Ascending type Ascending date Ascending name Ascending |
| 4 | progresses | userId Ascending date Ascending name Ascending |
| 5 | progresses | type Ascending date Descending name Descending |
| 6 | progresses | type Ascending userId Ascending date Ascending name Ascending |
| 7 | progresses | type Ascending userId Ascending date Descending name Descending |
| 8 | progresses | taskId Ascending date Ascending name Ascending |
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.
Assessment
This issue has not been assessed yet.