[Refactor][Database columns] Standardize component column type across all database tables
- Dominant language
- Go
- Stars
- 3.1k
- Forks
- 808
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 49
Description
## What and why to refactor
Several tables contain a column named component, but the column definition is not consistent across the schema.
Columns representing the same business concept (component) should ideally share a common data type and sizing strategy across the database schema.
Diferent types identified:
- VARCHAR(100)
- VARCHAR(191)
- VARCHAR(255)
- VARCHAR(500)
- TEXT
## Describe the solution you'd like
Review all database tables containing a component column and standardize them using a single data type.
Suggested type ```TEXT```
## Related issues
https://github.com/apache/devlake/issues/8993
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by searching the database schema and migrations for every table containing a component column, and review related issue #8993 for context. Compare the existing VARCHAR and TEXT definitions, standardize the identified columns to TEXT, and run the relevant database or schema validation tests to confirm the full schema is consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- database
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100