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
Currently there is a table named recentEpisodesByCategory and 30 "temp" tables used in the indexing process for recentEpisodesByCategoryTempXX.
This is a mess, and not a proper solution. We need to replace whatever purpose these tables have with a single table, or index on an existing table, or a materialized view, or ?
This will require changes to both the database and the API.
The text was updated successfully, but these errors were encountered:
Currently there is a table named
recentEpisodesByCategory
and 30 "temp" tables used in the indexing process forrecentEpisodesByCategoryTempXX
.This is a mess, and not a proper solution. We need to replace whatever purpose these tables have with a single table, or index on an existing table, or a materialized view, or ?
This will require changes to both the database and the API.
The text was updated successfully, but these errors were encountered: