I'm adding a feature to traffic ops that creates a new column in steering_target called type, that is populated with type ids from the type table. Using admin.pl upgrade, the column is created in migrations, and the two types for this table are populated by seeds.sql. None of this is out of the ordinary. Unfortunately I also need to populate the type column based on data that isn't in there until after seeds.sql is run, so I can't place this into the migration. Seeds.sql needs to run after the migration due to any structural changes that happen there.
Dewayne and I have discussed this a bit this morning, and we're thinking the best solution might be a third step, run after seeds.sql, called patches.sql. This would be specifically for data fixes like in this use case. The order would be as follows: migration - structure seeds - static data patches - data fixes Thoughts? Derek
