Re: [Gnumed-devel] installing and using gnumed

[Ian Haywood]

On Sat, Nov 01, 2003 at 10:22:33AM -0700, Roberto Mello wrote:
> On Fri, Oct 31, 2003 at 09:02:15PM +0100, Karsten Hilbert wrote:
> > Most of them are warnings that PG reports as errors and result
> > from dropping non-existant DB objects (with halt-on-error
> > temporarily off). They *do* hide the real errors which is
> > unfortunate but to the best of my knowledge not avoidable.
> 
I have written a Python replacement for psql, see 
/gnumed/gnumed/server/bootstrap/Psql.py

Still ironing out some bugs before intregrating with the main script,
this gives us more control over the process, spurious errors can be directed at 
/dev/null.

I also propose some simplifications to the script
        - making an effort to find files for sql and modules, to avoid needing 
to set up links
        - not prompting for the postgres password if we don't need it (as most 
users
will have no idea what it is)
        - offering to overwrite postgres config files with a sensible default 
setup.
        - removing the "yes or no" question, it just gets in the way, users can 
press 
Ctrl-C at the gmdb-owner password prompt if they want to quit.


> 1) User runs bootstrap script
> 2) bootstrap script notices that things are already installed, at least
>    partly 
> 3) bootstrap script asks user if s/he wants to DROP everything and start
>    from scratch
good idea, but probably simpler just to rename the old database to "old-gnumed"
and start afresh. This way data cannot accidentally be destroyed.


Ian
-- 
PGP public key E750652E at wwwkeys.pgp.net
9BF0 67B7 F84F F7EE 0C42  C063 28FC BC52 E750 652E

pgpHtKDTbjiQn.pgp
Description: PGP signature