[Top][All Lists]

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

[Gnumed-devel] NOT clin_root_item !!

From: Karsten Hilbert
Subject: [Gnumed-devel] NOT clin_root_item !!
Date: Mon, 26 May 2003 17:43:19 +0200
User-agent: Mutt/

Before we go down the wrong road:

No one is supposed to store anything in clin_root_item ! Just
as the docs say:

 comment on TABLE clin_root_item is
        'ancestor table for clinical items of any kind, basic
         unit of clinical information, do *not* store data in
         here directly, use child tables,
         contains all the clinical narrative aggregated for full
         text search, ancestor for all tables that want to store
         clinical free text';

Rather use clin_note, a generic child of clin_root_item.

 create table clin_note (
        id serial primary key
 ) inherits (audit_mark, clin_root_item);

 comment on TABLE clin_note is
        'Other tables link to rows in this table if they need
         more than their one inherted narrative field for free text.';

The reason for this being that one cannot do:

create table clin_root_item() inherits (audit_mark);
create table clin_some_other_item() inherits (audit_mark, clin_root_item);

Just having clin_some_other_item inherit the audit property
and columns from clin_root_item doesn't work with automatic
audit trail generation since the get_children query only finds
direct descendants not arbitrary depths leafs.

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]