[Gnumed-devel] database installer

[Hilmar Berger]

Hi,
Ian Haywood wrote:
>Would anyone onject to the client firing up the GUI installer if it finds
its trying to connect to an empty database?

This will only solve our problem in the case a) postgres is properly
configured and running and b) the user actually wants a local installation
at all. 

IMHO this should go in some installation script ("Setup") and not be
automatically fired up if for some reason a local database named "gnumed" is
not accessible (you can only check this after loggin on, so this would mean
somewhere in gmGuiMain, wouldn't it ?). 

I would suggest a clean separation of Setup and the rest of gnumed.
It should work like this (resembling other setup procedures):
- in general, new users are advised to run Setup when trying to run gnumed
the first time
- Setup checks if gnumed-DB is present and accessible (postgres
configuration check) and gives some hints on how to configure postgres
- if no gnumed database is present or it is empty and the user wants a local
backend, fire up the database installer
- when backend install succeeded ask the user if gnumed should be started
right now 

If, in the client, a database connection to local "gnumed" is tried but no
backend is found show a message what is wrong and that "Setup" should be run
before working on a local DB is possible and exit.

IMO wizard-like inclusion of database installation is no clean approach.
There will be some cases where it works, and some where it just makes things
more complicated than should be. 

Hilmar



-- 
250 MB Mailbox, 100 FreeSMS/Monat, 1000 MB Online-Festplatte
Jetzt GMX TopMail kostenlos testen http://www.gmx.net/de/go/topmail