gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] 0.3-rc4 released


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] 0.3-rc4 released
Date: Sun, 17 Aug 2008 23:11:54 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Sun, Aug 17, 2008 at 05:58:44PM -0300, Rogerio Luz wrote:

> > People really need to think of database and client being to
> > *separate* things which can exist and make sense independant
> > of each other on any machine.
> 
> Ok I see it now ... so the bootstrap will NEVER delete the database v9,
The *upgrade* will never delete it -- unless you upgrade *to*
gnumed_v9. Otherwise the upgrade would not make sense.

If you run bootstrap-latest.sh that will re-bootstrap all
the way from _v2 to _v1384 if necessary. In that process it
WILL delete _v9 if it exists.

> but
> if I have a v27 running in the CVS and one day the bootstrap needs to make a
> v27 to work on my REAL patients it WON´T import all the nonsense form the
> CVS v27 database?
The conclusion is true but there is no difference between a
"CVS database" and a "real patients database".

There is only one gnumed_v27 ever. It does not matter how it
was bootstrapped:

- via some sort of package
- via the GNUmed-server.v27.tgz
- via a later GNUmed-server.v378.tgz

It will always be the same database. And if the gnumed_v27
already exists it will be deleted.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346




reply via email to

[Prev in Thread] Current Thread [Next in Thread]