about summary refs log tree commit diff stats
path: root/db/migrate/20170930213633_rename_revision_hold_item.rb
Commit message (Collapse)AuthorAgeFilesLines
* Fixed migration againKelly Rauchenberger2017-10-151-1/+1
|
* Changed the way that the hold item column is migratedKelly Rauchenberger2017-10-151-1/+3
| | | | | | | MySQL seems to choke on the previous way that the hold_item column became the item_id column; since this is an old migration and would only be run retroactively anyway, we can change this to just dropping the hold_item column and adding the item_id column.
* Added hold itemsKelly Rauchenberger2017-09-301-0/+9
An items model was created, but the seed only contains items that can be held, which excludes key items and HMs. Berry Juice, while unobtainable, is still included. The item model contains three description fields: one for Ruby/Sapphire, one for FireRed/LeafGreen, and one for Emerald. This is because the descriptions for items are different between the games. In a lot of cases, the Emerald description is the same as the Ruby/Sapphire one, so in those cases, the Emerald description is nil. The purpose of having the different descriptions is so that when a Pokémon holds an item, the website can display the description that is accurate to the game that that Pokémon is currently in. In order to fully support TMs, the move model was improved to additionally contain type and also the three description fields which operate similarly to those of the item model. For TMs, the description fields on the item are usually nil. However, some TMs in Ruby/Sapphire, as well as Emerald, have different descriptions than the moves that they correspond with. In these cases, those descriptions are in the item model, and override the move descriptions when the move is looked at as a TM.