l3montree-dev / l3montree-dev/devguard
Adjust AssetVersion and Artifact Identifier columns
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
For the asset versions we currently use a composite primary key consisting of the name and the assetID.
For the Artifacts we currently use a composite key consisting of 3 columns (assetID,avName and artifactName).
We could migrate both to 1 id column per av/artifact.
This would make the data schema way more consistent and makes referencing those way less akward which in return also improves performance on a lot of tables by taking up less space.
Performance is a feature
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
Start by locating the AssetVersion and Artifact schema definitions and every reference to their current composite keys. Trace how migrations and related tables use these identifiers; done means both entities use one id column consistently and existing references and data remain valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100