gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] Hacking a development database


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Hacking a development database
Date: Sat, 3 Dec 2011 10:50:37 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Fri, Dec 02, 2011 at 12:03:21AM +0000, Jim Busser wrote:

>         ./createdb -U postgres -O gm-dbo -T gnumed_v16 gnumed_v17

...

> wherein I had taken my production v16 conf and replaced
> all occurrences of 16 to 17. While it seems that the 1.1.5
> client *will* accept to connect,

Only if run with --debug.

> I get the following and
> wondered whether it speaks to anything additional (or
> better) that I should do when testing out the client against
> a cloned database (whose schema, until I would try to revise
> it, would be the same as for v16).

There's not really a need to do anything about it for a
development database.

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346



reply via email to

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