Hi Dimitry,
We are using the same approach as ?Bert (storing compositions, not versions) using Oracle 11.2.0.4.0 and it's working fine. We use openEHR schemas (Composition, Content, Structure and BaseTypes) with slight modifications (datetime regexp, for example). --- Jacobo ________________________________ De: openEHR-technical <openehr-technical-bounces at lists.openehr.org> en nombre de pazospablo at hotmail.com <pazospablo at hotmail.com> Enviado: viernes, 17 de abril de 2015 05:25 Para: 79104301700 at yandex.ru; openehr-technical at lists.openehr.org Asunto: Re: OpenEHR and Oracle XML DB problems 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<mailto:<[email protected]>> Date: Thu, Apr 16, 2015 04:06 To: For openEHR technical discussions; Subject:Re: OpenEHR and Oracle XML DB problems Hi Bert,I give up. The problem appears in 12c as well. And people agree that it is an Oracle bug.ht<http://bug.ht>tps://community.oracle.com/message/13008017<http://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<mailto:%20baranovda at yandex.ruPh>: 7 910 430-17-00<tel:7%20910%20430-17-00>_______________________________________________openEHR-technical mailing listopenEHR-technical at lists.openehr.orghtt<mailto:%20listopenEHR-technical at lists.openehr.orghtt>p://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org<http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org> --- AVISO SOBRE CONFIDENCIALIDAD. La legislaci?n espa?ola ampara el secreto de las comunicaciones. Este correo electr?nico y sus anexos son estrictamente confidenciales. Si Vd. no es el destinatario del mismo, por favor, notif?quenoslo inmediatamente y destruya el original. No deber? copiar este mensaje ni sus anexos o usarlo para prop?sito alguno, ni divulgar su contenido a ninguna persona. ---- ---- --- WARNING ABOUT CONFIDENTIALITY. Spanish law guarantees privacy in electronic communications. This message and its attachments are confidential. If you are not the intended recipient please, notify us immediately and destroy the original. You should not copy this message or use it for any purpose, nor disclose its content to any other person. --- AVISO SOBRE CONFIDENCIALIDAD. La legislaci?n espa?ola ampara el secreto de las comunicaciones. Este correo electr?nico y sus anexos son estrictamente confidenciales. Si Vd. no es el destinatario del mismo, por favor, notif?quenoslo inmediatamente y destruya el original. No deber? copiar este mensaje ni sus anexos o usarlo para prop?sito alguno, ni divulgar su contenido a ninguna persona. ---- ---- --- WARNING ABOUT CONFIDENTIALITY. Spanish law guarantees privacy in electronic communications. This message and its attachments are confidential. If you are not the intended recipient please, notify us immediately and destroy the original. You should not copy this message or use it for any purpose, nor disclose its content to any other person. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150417/6650df7a/attachment.html>
