Re: [Gnumed-bugs] GNUmed 1.5.0 - invalid [v19] schema structure

[Busser, Jim]

On 2015-01-15, at 1:34 AM, Karsten Hilbert <address@hidden> wrote:

> So (in this case, because there _are_ fixups changing the hash
> between your v19 version and the final v19):
> 
>       cd server/bootstrap/
>       ./fixup-db.sh 19
>       ./upgrade-db.sh 19 20

So it would seem that, in relation to what I had recently been wondering (in 
relation to the 1.5.0 feature release) and where I had asked

>> can we do as above "from" 19.14 or would such a path
>> fail on account of failing to take care of the database fixup
>> scripts included in 19.15?
> 
> (which you had) rephrased as:
> 
>> can we do as above "from" 19.9 or would such a path
>> fail on account of failing to take care of the database fixup
>> scripts included from 19.9 to 19.14?
> 
> (and then answered)
> Given that: no it should not fail and yes you should be able
> to upgrade any v19.x to v20.0 because before attempting the
> upgrade all fixup scripts are run again just in case.

then while

        upgrade vX vX+1

should always work from

        vX.latest_in_the_vX_series

the case of a

        vX.nonlatest_minor release

one might often be *unable* to run the upgrade directly until having first done 

        fixup vX

in order to first bring

        vX.nonlatest_minor release --> vX.latest_in_the_vX_series

-- Jim