[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnumed-devel] re: gui / schema
From: |
sjtan |
Subject: |
Re: [Gnumed-devel] re: gui / schema |
Date: |
Tue, 20 Jul 2004 07:44:22 +1000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616 |
It already does. Look at Capt.Kirk. Ask if need be.
How do I get this example working?
All the tables I have worked on are fully audited. And the
audit results have been checked (manually) to contain what one
would expect. Auditing *does* work today.
Sorry , I'm not saying it doesn't work , I'm saying that auditing is
fine as a trigger, since it is transparent and
doesn't veto normal update . I just remember demographics
had a custom trigger which made insert/update look non-transparent. I think
it's fixed now. The point is that triggers and semantic and integrity
constraints
can make a schema more difficult to write insert/updates too, and , like
, say
workflow heuristics, may be a point of contention.
indentity2_extid is obviously useful, because it just allows subtypes
of ids : different country's public health id,
different pathology company or hospital patient id. The xlnk_identity
seems less useful,
and the concept of true pupic is like God saying sorry about the tower
of babel ( sorry I'm not religious).