Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added notion of targetVersion #1

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

mpollmeier
Copy link

Hi Graham,

I forked and amended dbdeploy to have the notion of a target version. Depending on the current version and we either perform an upgrade or downgrade. Theirfore I slightly amended the Ant API. Please have a look and let me know your thoughts!

Best regards, greetings from Cardiff
Michael

@tackley
Copy link
Owner

tackley commented Feb 28, 2011

Hi Michael,

Apologies for taking so long to look at this, I haven't had chance to focus on dbdeploy for far too long. But I'm looking again now :) Thanks for the pull request!

This looks like a great simplification to dbdeploy, removing a lot of the clumsiness around undo scripts and "last change to apply". From the looks of it we can no longer generate an undo file, which makes a lot of sense, but I'm going to ask on the user list whether anyone desperately needs this feature before I pull. targetVersion makes a lot more sense and does everything and more, but I'm always nervous of taking features away...

And greetings from Kings Cross!
g

@mpollmeier
Copy link
Author

Nice one, thanks for looking into this.
Greetings from the far west ;)

@mpollmeier
Copy link
Author

bump
Any reactions on the user list in the last couple of months? ;)
Would be nice to have this in the main line of dbdeploy...

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.

2 participants