When you step through migration steps, your model class might not correspond to the fields in the database for previous migrations. Let's say at a later point you change the model, and this older migration needs to run, it might fail because you've added validation logic or subsequently altered/removed a column that it's trying to migrate.
Does this gem do
query_trace
style logging? What's the current fancy option for that?When you step through migration steps, your model class might not correspond to the fields in the database for previous migrations. Let's say at a later point you change the model, and this older migration needs to run, it might fail because you've added validation logic or subsequently altered/removed a column that it's trying to migrate.