Card Binder Schema Changes #495

New issue

Open

opened 2026-04-28 17:49:48 +01:00 by Vylpes · 0 comments

Vylpes commented

2026-04-28 17:49:48 +01:00

Owner

Epic: #281
Story Points:

SO THAT I can save card binder info persistently

Acceptance Criteria

GIVEN I am a developer
WHEN the project is migrated
THEN the database schema will include the data required for the new Card Binder feature

Subtasks

Add BinderSlot entity and migration
Add tests
Add documentation

Notes

BinderSlot NEW
- id (PK, UUID)
- UserId (FK)
- PageNumber (int, 1..3) - Up to 3 for now so don't constrain in db
- SlotIndex (int, 1..9) - 1-based
- CardNumber (string)

Epic: #281 Story Points: --- SO THAT I can save card binder info persistently ## Acceptance Criteria GIVEN I am a developer WHEN the project is migrated THEN the database schema will include the data required for the new Card Binder feature ## Subtasks - [ ] Add `BinderSlot` entity and migration - [ ] Add tests - [ ] Add documentation ## Notes - BinderSlot NEW - id (PK, UUID) - UserId (FK) - PageNumber (int, 1..3) - Up to 3 for now so don't constrain in db - SlotIndex (int, 1..9) - 1-based - CardNumber (string)