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
        
After doing (from server 19.8 tarball)

        cd /Users/djb/Downloads/gnumed-server.19.8/server/bootstrap
        ./fixup-db.sh 19

I then tried from (from server 20.1 tarball)

        cd /Users/djb/Downloads/gnumed-server.20.1/server/bootstrap
        ./upgrade-db.sh 19 20

but it still complained

        2015-01-15 08:30:07 DEBUG gm.db 
(/Users/djb/Downloads/gnumed-server.20.1/Gnumed/pycommon/gmPG2.py::database_schema_compatible()
 #588): 2015-01-15 07:47:01.503023-08 - 19.8 - 
v19-find_potentially_misappropriated_soap-fixup.sql
        2015-01-15 08:30:07 ERROR gm.bootstrapper 
(./bootstrap_gm_db_system.py::__create_db() #771): invalid [v19] schema 
structure in GNUmed template database [gnumed_v19]
        2015-01-15 08:30:07 ERROR gm.bootstrapper 
(./bootstrap_gm_db_system.py::__bootstrap() #599): Cannot create database.
        2015-01-15 08:30:07 ERROR gm.bootstrapper 
(./bootstrap_gm_db_system.py::bootstrap() #1309): Cannot bootstrap bundle 
[v19_fixups-pre_v20]. 

and a fresh fingerprint of my v19 still gives the same fingerprint as before I 
(re) ran the fixups contained with 19.8

        9765373098b03fb208332498f34cd4b5

but on a hunch, I reran the fixups from within the ***20.1*** tarball after 
which the fingerprint became

        57f009a159f55f77525cc0291e0c8b60

which, on further perusal, is explained by the fact that after the release of

        ...gnumed-server.19.8/server/bootstrap/fixup_db-v19.conf

more fixups were added (presumably at 20.0, and therefore contained in 20.1) 
because the following file

        ...gnumed-server.20.1/server/bootstrap/fixup_db-v19.conf

had these additional fixups

        v19-bill-v_bills-fixup.sql
        v19-bill-bill_item-fixup.sql
        v19-dem-org-idx-fixup.sql
        v19-dem-v_orgs_v_org_units-fixup.sql
        v19-dem-v_praxis_branches-fixup.sql

as well as

        superuser/v19-install-pg_trgm.sql

so, when running

        ./upgrade-db.sh x x+1

is it manageable for the script to "call" (run) the fixup contained within the 
same directory level or is it incumbent on us to each time ensure to run, from 
whichever tarball we wish to represent the new version, both

        ./fixup-db.sh x
        ./upgrade-db.sh x x+1

??      

-- Jim