Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/145: Database Changes #150

Merged
merged 15 commits into from
Sep 12, 2023
Merged

Feature/145: Database Changes #150

merged 15 commits into from
Sep 12, 2023

Conversation

Nyzabes
Copy link
Contributor

@Nyzabes Nyzabes commented Sep 12, 2023

  • use the (currently empty) commits-stakeholders connection instead of the signature attribute in commits
  • use the (currently empty) issues-commits connection instead of the mentions attribute in issues
  • use the commits-commits connection instead of the parents/history attributes in commits
  • add commits-builds connection instead of using the sha/ref attributes in builds
  • see DB Issues #145

- instead of storing the signature of an author in the `signature` attribute of commits, a connection is used
- the frontend still uses the `signature` attribute, but it is inferred using the connection
- #145
- instead of using the `mentions` attribute in issues
- #145
- commits were not sorted with new localDB function, which broke the Changes/Version mode of the Code Hotspots visualization.
- #145
- instead of the `sha`/`ref` attributes in the builds collection, the commits-builds connection is used.
- #145
- Because the `builds` connection does not have a `sha` attribute anymore, the Histogram endpoint was broken both in the serverDB and the localDB.
- #145
- instead of using the `history` and `parents` attributes, the commits-commits connection is used.
- the graphql service infers the parents directly, as does the localDB when accessing commits. This means the `parents` attribute can still be queried, even if it's not in the DB anymore.
- query times are much faster, DB export files significantly smaller
- #145
- fixed bug where filepicker crashes when new files are added in the project directory but ownership has not yet been indexed
- when querying commits using the seerverDB, commits that are earlier than the specified earliest date should only be discarded after the history has been calculated for all commits. Otherwise, history calculation would not work properly.
- #145
- fixed bug where sprint visualization crashes when no sprints are defined
- also fixed minor styling/behaviour bugs of new TabCombo component
@nuberion nuberion merged commit e80b5ca into develop Sep 12, 2023
2 checks passed
@uberroot4 uberroot4 deleted the feature/145 branch September 28, 2023 13:58
@uberroot4 uberroot4 linked an issue Nov 3, 2023 that may be closed by this pull request
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DB Issues
3 participants