Comment 3 for bug 868197

Yeah, that makes sense. Now that I think about it, it may already just
work with the change you made to allow scripts to be added to a
version after it's been installed.

Can you try running dbversion create -v 4.9 and check whether it
already does what you want?

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

> Because they're attached to a particular release of the project. It's a
> long story but it’s just how we work.
>
> We work off trunk and add scripts into a directory that relates to the
> next release version - 4.9. As we get ready to release this, we branch
> off. People continue to work on trunk and will add scripts in as
> necessary to the next release version - 4.10. Scripts may also go into
> the branch at the same time. If we have some devs working on trunk
> they'll update their database to 4.10 and when 4.9 is re-integrated they
> won't be able to run the scripts that were added in the branch because
> the database has moved onto 4.10. In this case you kind of need a "I
> know what I'm doing checkbox" to allow the devs to force run any new
> scripts from the 4.9 branch.
>
> Does that make any sense?
>
> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Adam Connelly
> Sent: 06 October 2011 08:36
> To: <email address hidden>
> Subject: Re: [Bug 868197] [NEW] Create option for running scripts against non-current version
>
> Can you explain the scenario a bit more. I'm just wondering why you
> wouldn't just include the scripts in the next version, 4.11?
>
>
> On 5 Oct 2011, at 10:25, Colin Winning <email address hidden>
> wrote:
>
>> Public bug reported:
>>
>> 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.
>>
>> ** Affects: dbversion
>> Importance: Undecided
>> Status: New
>>
>> --
>> 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
>
> --
> You received this bug notification because you are subscribed to the bug report.
> 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
>
> --
> 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