Migrate `last_registry.dat` to SQLite
Open
- Dominant language
- Python
- Stars
- 670
- Forks
- 183
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 368
Description
Pickling is causing compatibility issues when there are added/removed object attributes and their lifecycles change.Let's replace it with a SQLite database to keep consistency across different versions with explicit schema.
Related with #489.
JIRA Issue: BA-265
Contributor guide
Research direction
Start by locating the code that reads and writes last_registry.dat, then review related issue #489 for context. Define the SQLite schema and migration requirements from the existing persisted data and lifecycle compatibility concerns. Done means registry data remains consistent across supported versions and the relevant persistence behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sqlite
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100