[Top][All Lists]

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

Re: [Gnumed-devel] (no subject)

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] (no subject)
Date: Wed, 25 Feb 2004 22:21:36 +0100
User-agent: Mutt/

> Well, instead of working on data validation how but starting with
> just connecting the gui schema with the sql schema WITHOUT validation
> or security; add those later.
a) I don't want to have "invalid" data in the backend right
   from the beginning if I can help it, invalid data kills my
b) We are ALREADY compromising: Our current data access
   security scheme (grouped rights mapped to grants) don't
   suffice for, say, HIPAA. Eventually we'll need row-level

> Security is what stuffs up the backend 
> initialization process,
Huh ? Even if so that's not a valid reason for not making it
part of the design.

> and validation ( or conflicts with perspectives 
> about what is valid schema) caused the demographics ui to schema 
> connection to be done and broken and re-done many times in the history 
> of this development.
Unfortunately so.

> Write a mapping specification , and then there will 
> be less mix-ups.
I'll try my best when time allows. Roughly there currently are
two schemes in use: a manual "mapping" done by me (seen the
vaccinations edit area) and a "defined" mapping done by you
(see PastHx I believe). Mine is cleaner code, acceptable and
works. Yours works, is way more elegant but isn't "clean" code.
What we need is clean and elegant code. We'll get there. Post

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

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