Database Optimization
Closed this issue · 0 comments
multimokia commented
Feature Description
Looking at our current database state, we could do with some optimization further down the line. This is technically low priority as ideally we should have somethng that works first and foremost, but once we do, we can look into extrapolating more common flows into functions and more importantly - View
s, which also respect RLS and likewise help us query subsets of data more quickly than iterating over a full database (the main use case I see here is for the messages
table, and as an example, we can move pinned messages for a given channel to their own view)
Use Case
Speed up and simplify queries on backend to ideally speed up user operations done on the front
Prerequisites
N/A
Any additional remarks:
N/A