Comment 7 for bug 868197

Ah well, worth a shot. Fancy updating the case with some example command usage?

On 11 Oct 2011, at 09:45, Colin Winning <email address hidden> wrote:

> OK. Tried forcing it to run tasks for the non-current database version
> and it doesn't work correctly. It checks what the current database
> version and only runs tasks for that and above. So an example:
>
> Run with -v "4.9"
> Current db version = 4.10
>
> Only looks for tasks for 4.10 and above.
>
> The desired behaviour would be to force it to run any new tasks for 4.9
> and ignore the fact it's at 4.10.
>
> --
> You received this bug notification because you are subscribed to DB
> Version.
> https://bugs.launchpad.net/bugs/868197
>
> Title:
> Create option for running scripts against non-current version
>
> Status in DB Version:
> New
>
> Bug description:
> It would be useful to have an option to run scripts for a previous
> version. An example is current database version is 4.10 but some
> scripts have been added to a previous branch (4.9). These scripts from
> 4.9 will now never run.
>
> I know this is probably a bit non-standard but would be a useful
> enhancement.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dbversion/+bug/868197/+subscriptions