[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnumed-devel] Psql.py and explicit begin/commit;
From: |
Karsten Hilbert |
Subject: |
[Gnumed-devel] Psql.py and explicit begin/commit; |
Date: |
Fri, 3 Dec 2004 17:43:39 +0100 |
User-agent: |
Mutt/1.3.22.1i |
Ian,
new clin_episodes that do not link to a health issue need to be
inserted inside a transaction now due to their pointing to a
clin_narrative which in turn points to the clin_episode.
Psql.py does not handle transactions as it just considers every
single statement to be one. Might we change it's behaviour to
allow for (or require if that's easier) explicit transactions ?
This is the reason the lab regression test data fail on
bootstrapping with Psql.py. Using psql on the command line
works just fine.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
- [Gnumed-devel] Psql.py and explicit begin/commit;,
Karsten Hilbert <=