This content has been marked as final. Show 3 replies
AFAIK xsd:any cannot be used in conjuction will elements with minOccurs="0". So your complete type would need to be
Each any will be mapped to a VARCHAR2 or CLOB. This will not save you any columns in underlying table. Maybe if you had multiple elements following number and mapped them to any with maxOccurs unbounded this would work.
<xsd:complexType name="WfInformation"> <xsd:sequence> <xsd:element name="Company" type="WfCompany" minOccurs="1"/> <xsd:element name="HeadOffice" type="WfOffice" minOccurs="1"/> <xsd:any processContents="lax"/> <xsd:any processContents="lax"/> <xsd:element name="Number" type="xsd:string" minOccurs="1"/> <xsd:any processContents="lax"/> </xsd:sequence> </xsd:complexType>
That said the any will cause problems with optimizaiton of XPATH queries against the XML, and should be avoided at all costs.
Can you send me the set of XMLSchemas and I'll run it through an internal tool that will identify a set of annotations that will avoid the 1000 column limiit.
Thanks. I think that leaves out my option to create a totally new Schema to suit my XML files.
Only other option we have is to use Annotations.
I think my colleague - eoin62 would have shared the XML Schema files earlier through your oracle email address.
Please refer thread - How to register multiple XSD files
But we received a reply and we knew very little on how to make changes to Admin.xsd and how would that solve our problem. Please correct me if i am incorrect. Because the biggest Schema was estimate.xsd that has close to 800+ elements. I am not sure if my colleague sent you the necessary tag names we use within the Schema. We have close to around 300 tags we use. But our combined XML Schema has close to 1600+ If we have to annotate, i thought it would be better we tell Oracle which tagswe need, which inturn should should help better create XMLtype table against a Schema and work on performance.
Your earlier reply was,
Basically in XML Schema Admin.xsd element AdminCompin WorkfileTypeneeds to be stored Out of line..
Add the annotations xdb:SQLInline=”false” and xdb:defaultTable=”ADMIN_COMP_XML”. to the element..
if you can share with our XML Schema on how to annotate or if you can share a location that shows how an annotated or non-annotated Schema works that would help us correcting our Schema files.
Thanks for all your support. We have gone a long way in XML Parsing in the last 6 weeks.
Edited by: beta32c on Feb 19, 2013 12:09 AM
Besides the analysis tool, Mark and his team created the "XDB Utilities" set of PL/SQL packages to easily be able to programatically change and update the XML Schemas with annotations and other things.
You can find and download the zip file (which also contains a "howto" pdf file) here:
(Oracle XML DB Manageability Packages - xdb_util.zip)