[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] Upgrade psql
From: |
Vaibhav Banait |
Subject: |
Re: [Gnumed-devel] Upgrade psql |
Date: |
Fri, 22 Nov 2013 10:12:07 +0530 |
I could get the abnormal entry. I have saved the medications without problem.
The important thing was it was accepted and was saved (bug, if it is mandatory
and can crash gnumed ). When I attempted to delete it, gnumed crashed. But I
could successfully edit it and save it. I hope the problem gets solved now.
Vaibhav Banait
-original message-
Subject: Re: [Gnumed-devel] Upgrade psql
From: Karsten Hilbert <address@hidden>
Date: 21/11/2013 9:10 pm
On Thu, Nov 21, 2013 at 08:48:48PM +0530, Vaibhav Banait wrote:
> select * from clin.v_substance_intakes where pk_episode = 555;
>
> Results in error clin.v_Substance_intake(s) - no such entry exist in database
Please try the following query against your v18 database:
select * from clin.v_pat_substance_intake where pk_episode = 555;
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
- [Gnumed-devel] Upgrade psql, Vaibhav Banait, 2013/11/16
- Re: [Gnumed-devel] Upgrade psql, Vaibhav Banait, 2013/11/20
- Re: [Gnumed-devel] Upgrade psql, Vaibhav Banait, 2013/11/21
- Re: [Gnumed-devel] Upgrade psql,
Vaibhav Banait <=
- Re: [Gnumed-devel] Upgrade psql, Vaibhav Banait, 2013/11/23
- [Gnumed-devel] Upgrade psql, Vaibhav Banait, 2013/11/24
- Re: [Gnumed-devel] Upgrade psql, Vaibhav Banait, 2013/11/24