We had a new developer join our project recently, and he needed his computer to be setup so he could run the application.
“Here is the svn repository, when you check it out, run these rake tasks.”
Unfortunately, is never that easy. This project setup revealed something about Active Record and migrations that I didn’t know about.
When I create a migration, I will often do data manipulation on the database, or pre-populate some fields with data needed for a lookup table. Lets look at a sample migration from a trivia game:
I want to add some sample questions, so that even if you don’t have your own questions, you will still be able to play the game. I added the method to the populate model, because I use it elsewhere in the code, and I try to keep it DRY. The populate method on the question model looks like this:
So, later on, I decided to add a degree of difficulty to the questions, so the players can get more points for answering harder questions. Here is what the migration looked like:
Of which I had to change the populate method on the question class to:
Then I ran my migrations, and continued development. Then when developer number 2 came across and checked out the project and ran the migrations, he got the error:
The problem is the old migration is dependent on the new model. All models in rails are just a mirror of the database, so the new model has a forward definition of the data. The code in the model knows about the rank field, but the schema of the database hasn’t caught up to create that portion of the mirror yet. This creates a little bit of a catch 22.
The rails wiki about migrations tells you to redefine the class to stop name conflicts. This would require me to make my migrations model agnostic, inserting straight to the database.
As a spoiled brat when it comes to databases and rails, I refuse to let go of my Active Record sugary syntax. Another solution I thought of is to just make the last change to question do the populate, and remove it from the previous versions. This will become a maintenance nightmare.
I came to the realization that I want to make a distinction between form and content when it comes to migrations. Form in this case is schema form, the changes to the database which reflect the data which the Active Records can potential hold.
Content is the specific data which is in the database. This distinction allows for me to use the power of my model classes in my data migrations, which is the place it is useful. It maintains backwards compatibility, because before I go touching the data, I have to make sure my schema is right.
What does this look like in Rails? I am not sure yet. Possibly saving the data migrations in each migration as a block and executing those at the end, only when you have the schema is correct. I am going to try it out!