Hi Diego,
That sounds like a sensible solution – does that mean it will need to be
represented with a different statement/grammar? What changes are necessary to
accommodate these kind of assertions? Sorry I’m not familiar with this.
Cheers,
-koray
From: openEHR-technical
> If a database has a field-type XML, then I expect it does something special
> with
> that field that justifies the fieldtypename.
Oh, it does, it offers validation of the XML, AFAICT.
Karsten Hilbert
___
openEHR-technical mailing list
If a database has a field-type XML, then I expect it does something
special with that field that justifies the fieldtypename.
Especially I expect that from Postgres, because they mostly do good things.
Bert
On 16-02-16 11:47, Thomas Beale wrote:
On 14/02/2016 23:25, Bert Verhees wrote:
On 16/02/2016 11:26, Seref Arikan wrote:
The document oriented view of the domain has no problem with storing
XML text in the DB, because the implementations are built against that
view. The clinical care focused use cases require developers to focus
on reading & writing documents, so there
You're right, it does not read in the way I wanted it to. Let me try to
clarify:
Clinical care is strongly single patient centric, and in most cases this
puts a limit on the amount of data that does not push the limits of
computational power too much. Developers can afford to fetch multiple
Hi Seref,
"so there is rarely a requirement to read across documents, because
clinicians would not be able to consume all that information at once
(except averages or other aggregate values they're interested in)"
I don't think that is true in any other than the most trivial
implementations. The
The document oriented view of the domain has no problem with storing XML
text in the DB, because the implementations are built against that view.
The clinical care focused use cases require developers to focus on reading
& writing documents, so there is rarely a requirement to read across
On 15/02/2016 10:25, Sebastian Garde wrote:
We have been through this a long time ago I think, with Koray having
the exact question and opinion I had.
The downside if you don't allow this kind of constraint(!) on
functional attributes in archetypes, here you cannot constrain the
other
On 14/02/2016 23:25, Bert Verhees wrote:
One doesn't know what software really does. One must distinguish what
software seems to do and what it really does.
Storing XML really as XML means, storing a lot of redundant
information. I don't know, but I cannot believe postgress really
stores
9 matches
Mail list logo
