On 16-04-15 09:06, Dmitry Baranov wrote: > Hi 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. Dmitry, if you read the post carefully, not people, but one person says, it *appears* to be a bug He has to escalate it to engineering, and if it is a confirmed bug, is something you must wait for He says he can reproduce it, this means he used your files.
I checked them also, they validate right in Oxygen. Oracle in different versions stumbling over your used OpenEHR XML Schema with your XML-instances? That is possible. There is a bug in a particular use of your schema. I am stressing to this because I am posting all the time Compositions in Oracle 12c, and all kind of other XML-instances from several namespaces. No problem at all. But I have things structured in another way. For example, when I post a Composition, the XML-instance starts with the Document-element called Composition. This is allowed because I have an xs:element COMPOSITION on top level in the XML-Schema (<xs:element name="COMPOSITION" type="COMPOSITION"/>). I noticed in a glance that you have that too, and it is logical that you have, because you flattened the same XML Schema's as I did. When you use that, you have to store your audit and version information elsewhere. When I look at your XML Schema and instance, just a quick glance, then I see that you have <xs:element name="version" type="VERSION"/> at top level, and derived from that Original Version, which has as child-element data of type xs:anyType. I would not do that, because you throw away any optimization. Oracle can't do anything with this. You could at least have it to be Locatable, because data in version are always of type Locatable. You could even have a original-version of type composition, and one of type party, this would help optimization even more. I regret that I cannot post the XML Schema and XML-instances I use, because they are not of my IP. But they are structured in another way, more dedicated to efficiency. Bert -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20150416/1fb69548/attachment-0001.html>
