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, 3 insertions, 1 deletions

@@ -10,7 +10,7 @@
 #
 # It's strongly recommended that you check this file into your version control system.
 
-ActiveRecord::Schema.define(version: 20180113200119) do
+ActiveRecord::Schema.define(version: 20180114170238) do
 
   create_table "pokeviewer_abilities", force: :cascade do |t|
     t.string "name", limit: 191, null: false
@@ -76,6 +76,8 @@ ActiveRecord::Schema.define(version: 20180113200119) do
     t.integer "slot"
     t.integer "location_id"
     t.string "pokeball", null: false
+    t.integer "current_id"
+    t.index ["current_id"], name: "index_pokeviewer_pokemon_on_current_id"
     t.index ["key"], name: "index_pokeviewer_pokemon_on_key", unique: true
     t.index ["trainer_id"], name: "index_pokeviewer_pokemon_on_trainer_id"
     t.index ["uuid"], name: "index_pokeviewer_pokemon_on_uuid", unique: true