gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] Re: [Gnumed-bugs] xDT import problems


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Re: [Gnumed-bugs] xDT import problems
Date: Thu, 18 Nov 2010 23:49:38 +0100
User-agent: Mutt/1.5.20 (2009-06-14)

On Thu, Nov 18, 2010 at 02:14:05PM -0800, Jim Busser wrote:

> > With PATIENTS.IN files GNUmed searches all available drive
> > letters for DRIVE:\MDW2\PATIENTS.IN *automatically* which is
> > bound to provide a lot of False Negatives. Hence they aren't
> > prompted to the user but rather logged only.

> The wiki says GNUmed will parse (at most only) two source
> files, one on the server and one locally ...

To tell the truth I don't know why it sayeth so. I've
currently got no idea why I wrote that or what I meant (or,
in fact, whether I wrote it ;-)

> so in the case
> of multiple drive letters would GNUmed ignore more than two
> positives?

No, it'll read all of them.

> > With MSVA sources OTOH, all of them are manually configured
> > so GNUmed pops up a message informing of the
> > misconfiguration.
> 
> Might it be meaningfully useful (performance-wise) and also (in the case 
> where a praxis would not use MSVA) to comment-out all of the inapplicable 
> sources?

GNUmed will scan all drive letters for \MDW2\PATIENTS.IN in
a hardcoded way so that's not even possible. I doubt it'll
make much of a difference anyway unless one of the drives is
a samba mount via dialup networking from across the Pacific.

Karsten
-- 
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346



reply via email to

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