CWorkflow for migrations?
The workflow for migrations in the documentation seems to indicate a very involved process for doing migrations.
1. Define the table with new optional fields.
2. Run the migration
3. Tighten up the table with the final version of the fields.
This seems extremely annoying. Surely there is a better way to do this? I want to the ability to do a deploy, have the migrations all run, and I'm not having to worry about manually doing every release. Are there any workflows for this that I'm not seeing?
It feels like in order to get my schema updated, we'll have to get our clients compiling with each step in the schema, instead of just the final product, and either manually go through this process of checking and releasing code for each step instead of just being able to rely on my data being in the final state. This seems like a massive headache.
Is there a better way to do this that I'm not seeing?
1. Define the table with new optional fields.
2. Run the migration
3. Tighten up the table with the final version of the fields.
This seems extremely annoying. Surely there is a better way to do this? I want to the ability to do a deploy, have the migrations all run, and I'm not having to worry about manually doing every release. Are there any workflows for this that I'm not seeing?
It feels like in order to get my schema updated, we'll have to get our clients compiling with each step in the schema, instead of just the final product, and either manually go through this process of checking and releasing code for each step instead of just being able to rely on my data being in the final state. This seems like a massive headache.
Is there a better way to do this that I'm not seeing?
