Comment 3 for bug 1163901

That sounds cool. I was going to say that we could just use a flag on
the create command except that you mentioned a mode where it doesn't
even hit the database.

The only thing I'd say is that you probably want to flip it round
slightly. The fact that we're doing a check rather than the full
create implies that we don't want to apply the changes, so instead of
having an option to specify whether you rollback or not, I'd have an
option to specify that we don't want to touch the database at all (-s,
--simulate maybe? You can probably come up with a better name).

Cheers,
Adam

On 3 Apr 2013, at 14:15, Donald Walker <email address hidden> wrote:

> Two 'modes' which seem they would be useful would be:
>
> Check-With-ListChangesButDontRunAnything
> Check-With-ExecuteAndRollback
>
> Which I think would be invoked on the command line as:
>
> # Display changes which would be made but don't actually touch the DB
> dbversion check -c constring -a archivedir
>
> # Do everything 'create' does, but rollback at the last moment
> dbversion check -r -c constring -a archivedir
>
> Any thoughts?
>
> --
> You received this bug notification because you are subscribed to DB
> Version.
> https://bugs.launchpad.net/bugs/1163901
>
> Title:
> Ability to test apply an upgrade
>
> Status in DB Version:
> In Progress
>
> Bug description:
> When apply an upgrade using the 'create' command, it would be great to
> be able to perform the create but at the last moment rollback. This
> would allow you to see what changes would be made, as well as
> verifying the actual create is likely to succeed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dbversion/+bug/1163901/+subscriptions