Change to model-specific vote tables
Registered by
Ken Arnold
The existing generic vote mechanism makes one huge table. It's hard to work with because Django can't query across a generic foreign key. I propose we make an abstract base Vote model, but specific vote models for each type of object (Sentence, RawAssertion, and Assertion for now). Another benefit is saving ~4 bytes per rating (that's a lot!) for not storing the object type.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
(?)