Re: [Gnumed-bugs] Log upgrading db v18 to v19

[Karsten Hilbert]

On Thu, Nov 14, 2013 at 03:57:28AM +0000, Jim Busser wrote:

This fact:

> > Does the client still fail against this database ?
> 
> Yes

and this fact:

> $ psql -d gnumed_v19 -U gm-dbo
> Password for user gm-dbo: 
> psql (9.1.10)
> Type "help" for help.
> 
> gnumed_v19=> \d dem.v_praxis_branches
>            View "dem.v_praxis_branches"
>            Column           |  Type   | Modifiers 
> ----------------------------+---------+-----------
>  pk_praxis_branch           | integer | 
>  praxis                     | text    | 
>  branch                     | text    | 
>  organization_category      | text    | 
>  l10n_organization_category | text    | 
>  unit_category              | text    | 
>  l10n_unit_category         | text    | 
>  pk_org                     | integer | 
>  pk_org_unit                | integer | 
>  pk_category_org            | integer | 
>  pk_category_unit           | integer | 
>  pk_address                 | integer | 
>  xmin_praxis_branch         | xid     | 
>  xmin_org_unit              | xid     | 
> 
> gnumed_v19=> 

Simply don't go together.

The view dem.v_praxis_branches cannot exist
and not exist at the same time (about which
the latter the client is complaining about
as per your posted console and log snippets).

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.

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