Re: [Gnumed-devel] bootstrapping database problem

[Florian Hubold]

Karsten Hilbert schrieb:
> Absolutely !
>
> Everyone please test the server package on their
> distribution so we can fix any remaining problems !-)
>   
Wouldn't it be more effective to open a new thread for this, so this catches
attention of more people? I guess not all read this thread until the end ...
>   
> > Also attached the logs from the bootstrapping process which now
> > succeeds. Yay! 8-)
> >     
>
> Yo !  Congratulation and thanks for the persistence. That's
> how open source works.
>
> BTW, the next version features a "quiet" command line option
> such that you can shut up the GNUmed bootstrapping script ...
>
> Karsten
>   
That would be my last question:
There is a patch in the gnumed-server package which disables interactively
runnning the bootstrapping script. But there is still the question asked:

   1) Dropping old baseline gnumed_v2 database if there is any.
   Signal an Server gesendet
   Datenbank »gnumed_v2« wird unwiderruflich gelöscht werden.
   Sind Sie sich sicher? (j/n) j
   dropdb: Löschen der Datenbank fehlgeschlagen: FEHLER:  Datenbank
   »gnumed_v2« existiert nicht

This is not good for rpm installs, they should never be interactive.
Why not check before asking to drop the database, if there is one existing?
Then that question would only come up if there is already a v2 database.

The patch does this:

   --- GNUmed-v8/server/bootstrap/bootstrap_gm_db_system.py.orig   
   2008-01-25 13:05:37.000000000 -0500
   +++ GNUmed-v8/server/bootstrap/bootstrap_gm_db_system.py   
   2008-01-25 13:08:17.000000000 -0500
   @@ -1190,6 +1190,8 @@
            _interactive = True
        elif tmp == "no":
            _interactive = False
   +    # we do not want to run interactively
   +    _interactive = False



Rather implement some checks whether there is already a gnumed-server
package and whether there is already a database. The first one i can handle,
for the second one i need help. Then we can implement some mechanisms
in the rpm to enable automatic staged updates.