My DBA is worried that scripts might be modified once they've already been run.
dbdeploy isn't the right place to try to enforce this, of course - we'll put
some kind of pre-commit hook in place in git so that our devs can't do this by
accident, and that we'll know if they do it deliberately. But...
It might be useful of dbdeploy could be aware that this had happened. If a hash
was stored in the change log table for each script as it was executed, it would
be possible to generate a report of any deltas that aren't the same as they
were when they were run.
I'd be happy to implement this. Any interest?
Original issue reported on code.google.com by simon.br...@gmail.com on 28 Feb 2012 at 3:01
Original issue reported on code.google.com by
simon.br...@gmail.com
on 28 Feb 2012 at 3:01