a) real-world things
are almost always hierarchical compositions (due to our human way of
describing them)
you can store those in a relational schema. It seems to me that the
problem is that sql doesn't really make it efficient to do heirarchical
type things with them. I know some old data
On Mon, 2007-11-05 at 06:18 -0500, Greg Caulton wrote:
Of course that would break if a new data element was added in a
position (fabricated)
data[at0001]/events[at0099]/data[at00100]/items[at0004]/value but the
simplicity is tempting.
This is of course why you should (IMHO) change your focus
One reason for the question was that it wasn't clear whether the
at uniquely identifies a concept within the ADL. I think it still
does, but it can have different context depending on where it occurs.
Implementing a hierarchy of information (information model) using
entity relationships
Why?
(Not that I intend to do that)
Gerard
-- private --
Gerard Freriks, MD
Huigsloterdijk 378
2158 LR Buitenkaag
The Netherlands
T: +31 252544896
M: +31 620347088
E: gfrer at luna.nl
Those who would give up essential Liberty, to purchase a little
temporary
Safety, deserve neither
On Mon, 2007-11-05 at 19:25 +0100, Gerard Freriks wrote:
Why?
(Not that I intend to do that)
On Nov 5, 2007, at 1:20 PM, Tim Cook wrote:
(please do NOT use MySQL for healthcare
information)
I will assume that your WHY? question was in response to this
statement I made?
In
Tim Cook schreef:
On Mon, 2007-11-05 at 19:25 +0100, Gerard Freriks wrote:
Why?
(Not that I intend to do that)
On Nov 5, 2007, at 1:20 PM, Tim Cook wrote:
(please do NOT use MySQL for healthcare
information)
I will assume that your WHY? question was in
6 matches
Mail list logo
