Chore: Use statuses
[in-memory] in auth
#245
Labels
chore
a tedious but necessary task often paying technical debt
priority-2
Second highest priority, should be worked on as soon as the Priority-1 issues are finished
T1h
Time Estimate 1 Hour
tech-debt
A feature/requirement implemented in a sub-optimal way & must be re-written
technical
A technical issue that requires understanding of the code, infrastructure or dependencies
At present, because of the way
Ecto
pre-loads the statuses we get this kind of noise:This is super noisy/annoying when trying to debug.
So ... rather than storing the
statuses
in the DB,I propose we use the dwyl/statuses package we recently created
and remove the
status
schema/table from theauth
project!Todo
The Entity Relationship Diagram (ERD) currently looks like this:
The
statuses
table isn't particularly big:But the more I look at it and think about how infrequently it will be updated,
the more I think it should just be a static
Map
that is compiled and in-memoryinstead of requiring a DB
JOIN
for every query! ⏳The text was updated successfully, but these errors were encountered: