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
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: /bugs.launchpad .net/bugs/ 868197 /bugs.launchpad .net/dbversion/ +bug/868197/ +subscriptions
>
> 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:/
>
> 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:/