Suppose the import is run multiple times, and MTGJSON has updated some cards' data in the interim. Unfortunately, these changes will not be picked up by the import script. This is especially obvious from the fact that, under current conditions, our latest field (loyalty) will not be added to any existing Card objects.
As a side consequence, the initial_import.py file should likely be renamed.
This would also be a good opportunity to make sure {sub,super,}types are handled properly for existing Cards -- all types should be cleared from the existing Card, then re-added based on the data.
Suppose the import is run multiple times, and MTGJSON has updated some cards' data in the interim. Unfortunately, these changes will not be picked up by the import script. This is especially obvious from the fact that, under current conditions, our latest field (
loyalty
) will not be added to any existingCard
objects.As a side consequence, the
initial_import.py
file should likely be renamed.