Hi Dmitry, as a side conceptual note, the openEHR IM is not a persistence
model, and the XSDs are a way to express instances of the IM.?
The XSDs would require some refactoring work to express an specific persistence
model for the Information Model, like simplifying some datatypes of the IM into
datatypes used/supported by your persistence technology, like dates, texts,
coded texts, ordinals, etc.
?I would suggest to explore hybrid approaches using relational+xml or
relational+json persistence technologies. It might make your work easier.
Cheers,Pablo.
Sent from my LG Mobile
------ Original message------From: Dmitry Baranov<79104301700 at
yandex.ru>Date: Thu, Apr 16, 2015 04:06To: For openEHR technical
discussions;Subject:Re: OpenEHR and Oracle XML DB problemsHi Bert,I give up.
The problem appears in 12c as well. And people agree that it is an Oracle
bug.https://community.oracle.com/message/13008017> You should always follow the
standard in your analyses, before you> declare one product buggy and another
not.> I see in that message that there was a patch recommended, did you try>
that? Always use the latest patch level.-- Regards, DmitryE-mail: baranovda at
yandex.ruPh: 7 910
430-17-00_______________________________________________openEHR-technical
mailing listopenEHR-technical at
lists.openehr.orghttp://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150417/001759bf/attachment.html>
