There are methods to make this work, but it would not work exactly like you propose.
You would in effect run multiple migrations against the same database. The first migration would only have scripts in it that include up to the one you want before the convert.exe would run. Then you would finish that migration and run your executable. Then you would call a second migration that would include the other scripts.
This solution however doesn't scale well and could start to get out of control depending on how many times you would need to stop and run the executable.
____
On Fri, Feb 15, 2013 at 11:13 AM, Steve W
<wrigh...@gmail.com> wrote:
We are looking to use RoundhousE, but we sometimes have a need to execute a small app to add security hashes to fields we are creating. Does RoundhousE support executing the up scripts to a specific number, where it would stop and we can run the executable, then continue on the remaining up scripts?
Here's an example:
0038_add_hash_to_student_record.sql
ConvertExistingData.exe
0039_something_else_to_migration.sql
Does this functionality exist where 0038 would be the last script to run, we execute the app, then we run RH again?
--
You received this message because you are subscribed to the Google Groups "chucknorris" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chucknorrisframe...@googlegroups.com.
To post to this group, send email to chucknorri...@googlegroups.com.
Visit this group at http://groups.google.com/group/chucknorrisframework?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.