Cached a Pokémon's latest revision

This removes the need to use a GROUP or DISTINCT in eager-loading Pokémon on the front page. It duplicates data, but provisions are in place to keep the cache up-to-date. When a Pokémon record is updated, it is required that its cache points to the current revision. When a revision is created, it updates the Pokémon's cache to point to it, because a new revision will always be the most recent one, and it is impossible to reorder revisions.

This does not affect the number of queries used on the front page (see #1).

refs #4

1 files changed, 1 insertions, 2 deletions

@@ -7,8 +7,7 @@ module Pokeviewer
         order(trainer_id: :asc).
         order(box: :asc).
         order(slot: :asc).
-        select(:uuid).distinct.
-        order("pokeviewer_revisions.sequential_id DESC").
+        joins(:current).
         includes(:current).
         chunk do |p|
           if p.trainer_id.nil?