thunderbird / thunderbird/thunderbird-android
Improve database structure
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Raising from #769 comments
Expected behavior
Database structure should be documented, logical, split into small, easily maintainable tables.
Actual behavior
Database structure is hard to follow, hard to maintain and fragile. Classes like the MessageListFragment do a single query to retrieve all their data and it's hard to know how well this is tested (probably badly
Steps to fix
- Document current database structure.
- Test MessageListFragment cursor API and other similar core classes, extracting code where necessary
- Write improved database structure
- Write migration step
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 documenting the current database structure and reading MessageListFragment's cursor API and similar core classes. Check how these queries are tested, then define the improved table structure and the migration step. Done means the structure is documented, core cursor behavior is covered by tests, and existing data can be migrated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- databases, mobile
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100