Skip to content

Conversation

@markltbaker
Copy link

As per my post in DBDeploy-users (I didn't realise that one could also send a message in github)

I've added the ability to do a 'fake' migration in the CLI with the --fake option. This works in both direct-to-db and generating script modes.

I've also added the --lastChangeToApply parameter to the CLI, which was already implemented, its just wiring up the command line parsing.

I've added / expanded unit tests for this and it all seems to be working locally as well.

So hopefully it's useful!

@markltbaker
Copy link
Author

Updated: this is now in use, but I realised I needed to add options to the Ant task as well. 'fake' turns on/off fake migrations and 'quiet' turns on/off the per-statement messages from the direct to db applier, because we had a lot of legacy sql scripts to use that had many statements in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant