Closed ogallagher closed 4 years ago
Top rated, editor’s choice, and top played collections are now all implemented in the backend. The frontend loads them, but the puzzle thumbnails don’t display all the information and are not interactive yet.
Puzzle thumbnails display necessary info and are now interactive.
The gallery page lacks a lot of functionality. The first step is to enable puzzle collections: top rated puzzles, editor’s picks, most played, etc. In general, these collections will not correspond directly to db tables, but rather be different selected table joins (ex: top rated = order puzzles by rating, pick top 15; most played = group plays by puzzle, order by count, join with puzzles and pick top 15).
Because of this the operations, though called repetitively, may be computationally expensive for the db. Therefore my plan is to consider each collection as a candidate for a view, which I believe could increase the speed greatly, especially in the case of most-played.
EDIT: Views do not save computation; they are recalculated everytime they’re used, I believe... so it appears I don’t really need to use views for this.