[Top][All Lists]

[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 22:24:27 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Sun, Aug 17, 2008 at 04:54:38PM -0300, Rogerio Luz wrote:

> > As many as you want and your hardware supports.

> Ok so how do I access the old DB?

You start the matching client with an appropriate config
file which defines a profile for that database.

> For example I want to to start working
> with the 0.3 client on my new DB, gnumed_v9.
If you locally unpack the tarball and start GNUmed locally
(with the from inside the tree) everything
should just work.

> Say in a few months we can make
> it to GNUmed 1.0 with gnumed_1.0
> I want to know how to access the "old" v9, say something bad
> happens with the bootsptrapping.
Well, you can *still* just run the from the
old local v0.3 tarball if the gnumed_v9 database is still

> My problem is that if I upgrade to DB v9 on my actual computer now with the
> stable 0.3 version, the CVS will likely be termed v10 ...
The next database, for the 0.3+ release, yes.

> but when I upgrade
> again ... say to GNUmed 1.0 ;) ... what happens to the v10 DB?
It will just stay where it is. The database will than be,
say, gnumed_v37 or whatever.

> Won´t it be conflicting with the one already being used by the CVS?
No, by default it will have a different name.

> Are they different?
Sure. First by name and second by content.

> Did I make sense?
Sort of. You'll know in case my answers answer your questions :-)

> I had this discussion in the devel list a few days ago ... but I am still
> confused ... in CVS the local database is installed INSIDE the CVS folder?
No, in the PostgreSQL data folder as any other database.

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.

> And in the .deb package where is it?
There is no .deb for the database so far.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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