[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-bugs] Log upgrading db v18 to v19
From: |
Karsten Hilbert |
Subject: |
Re: [Gnumed-bugs] Log upgrading db v18 to v19 |
Date: |
Thu, 14 Nov 2013 05:58:32 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Thu, Nov 14, 2013 at 04:40:52AM +0000, Jim Busser wrote:
> >> I maintain my rather heretic suspicion that
> >> you are not connecting to the database you
> >> think you may be connecting to. I will
> >> review the log on that.
> >
> > And, indeed:
> >
> > 2013-11-12 20:26:11 INFO gm.db
> > (/Users/dad/Downloads/gnumed-client.1.4.0/Gnumed/pycommon/gmPG2.py::set_default_login()
> > #477): setting default DSN from [None] to [dbname=gnumed_v18
> > host=127.0.0.1 port=5432 user=any-doc password=� sslmode=prefer]
>
> Oops! My 'bad', I had incorrectly assumed that
>
> gm-from-vcs.conf
>
> would by default be pointed to v19 on account of what I had expected would be
> incompatibility with v18, which appears to be the case.
>
> MIght it therefore be reasonable that in client
>
> ≥ 1.4.1
>
> we can have
>
> database = gnumed_v19
It *must* be _v19.
Are you saying the *tarball* came with an incorrect setting ?
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
- [Gnumed-bugs] Log upgrading db v18 to v19, Busser, Jim, 2013/11/13
- Re: [Gnumed-bugs] Log upgrading db v18 to v19, Karsten Hilbert, 2013/11/13
- Re: [Gnumed-bugs] Log upgrading db v18 to v19, Busser, Jim, 2013/11/13
- Re: [Gnumed-bugs] Log upgrading db v18 to v19, Karsten Hilbert, 2013/11/13
- Re: [Gnumed-bugs] Log upgrading db v18 to v19, Karsten Hilbert, 2013/11/13
- Re: [Gnumed-bugs] Log upgrading db v18 to v19, Busser, Jim, 2013/11/13
- Re: [Gnumed-bugs] Log upgrading db v18 to v19, Busser, Jim, 2013/11/13
- Re: [Gnumed-bugs] Log upgrading db v18 to v19, Karsten Hilbert, 2013/11/14
- Re: [Gnumed-bugs] Log upgrading db v18 to v19, Busser, Jim, 2013/11/14
- Re: [Gnumed-bugs] Log upgrading db v18 to v19,
Karsten Hilbert <=