docs: update README with database schema and priority calculation strategy
This commit is contained in:
parent
32321e9167
commit
49c42f76af
1 changed files with 8 additions and 0 deletions
|
|
@ -1 +1,9 @@
|
|||
# PieVR
|
||||
|
||||
## Database Schema & Core Concepts
|
||||
- **Storage:** SQLite (`storage/` directory, ignored in `.gitignore`).
|
||||
- **Tables:**
|
||||
- `questions`: stores core question data (`id`, `type`, `question_text`, `payload` as JSON, `active`, `last_asked_at`, `streak`, `times_asked`, `times_correct`, `created_at`).
|
||||
- `tags`: tags for granular and cross-cutting topic selection (`id`, `name`).
|
||||
- `question_tags`: many-to-many relationship between questions and tags.
|
||||
- **Priority & Spaced Repetition:** No hardcoded calendar intervals. Priorities and scheduling metrics are stored as raw counters (`streak`, `times_asked`, `last_asked_at`) in the database, while complex priority/decay formulas are calculated dynamically on the fly in Go.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue