You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doing scoring thorugh a Materialized View is nice from a DB point of view, however it causes some problems in practice:
Nobody besides @siccegge really understands the SQL, let alone is able to change it
Django doesn't know of Materialized Views, so it has to be deployed separately after initial database creation
The View's current schema is not optimized for rendering the scoreboard HTML, that still requires some processing in Python (see scores() in "calculations.py")
I want something more maintainable, probably more Python instead of SQL.
The text was updated successfully, but these errors were encountered:
F30
added
the
idea
Idea to be discussed, not yet ready for implementation
label
Jun 15, 2018
F30
added
improvement
Not a critical bug, but also not a visible feature
and removed
idea
Idea to be discussed, not yet ready for implementation
labels
Jul 11, 2020
Doing scoring thorugh a Materialized View is nice from a DB point of view, however it causes some problems in practice:
scores()
in "calculations.py")I want something more maintainable, probably more Python instead of SQL.
The text was updated successfully, but these errors were encountered: