Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


FW: Error: "The same table (tableName) cannot be the child table in two nested relations"

From: "firas" <firas@----.---->
To: <xmlschema-dev@--.--->
Date: 4/17/2004 2:32:00 PM
Hello:
 
Since Dfg was repeated under two different elements:
 
1-    squencia
2-    seq2
 
And Dataset Object for .net does not identify same element under two =
different elements
So just in case dfg have no attributes or child
Elements this can be done=E2=80=A6.
 
Regards
 
 
 
Firas Darweesh
Rapid Application Developer
Lootah IT Solutions
 
 
To: xmlschema-dev@w...
Subject: Error: "The same table (tableName) cannot be the child table in =
two nested relations"
 
Hi, I=E2=80=99m trying to load a schema into a .net program, but =
I=E2=80=99m getting this error:
=E2=80=9CThe same table (dfg) cannot be the child table in two nested =
relations=E2=80=9D
 
My schema is as follows: 
 
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" =
elementFormDefault="qualified" attributeFormDefault="unqualified">
       <xs:element name="teste">
             <xs:annotation>
                    <xs:documentation>Comment describing your root =
element</xs:documentation>
             </xs:annotation>
             <xs:complexType>
                    <xs:sequence>
                           <xs:element name="sequencia" =
type="sequenciaType"/>
                           <xs:element name="seq2" =
type="sequenciaType"/>
                    </xs:sequence>
             </xs:complexType>
       </xs:element>
       <xs:complexType name="sequenciaType">
             <xs:sequence>
                    <xs:element name="teste1"/>
                    <xs:element name="dfg" type="xpto"/>
                    <xs:element name="sdfhgfgh"/>
             </xs:sequence>
       </xs:complexType>
       <xs:complexType name="xpto">
             <xs:sequence>
                    <xs:element name="grrr" type="xs:gYearMonth"/>
                    <xs:element name="lsdkf" type="xs:duration"/>
             </xs:sequence>
       </xs:complexType>
       <xs:complexType name="comSeq">
             <xs:sequence>
                    <xs:element name="seqPP" type="sequenciaType"/>
             </xs:sequence>
       </xs:complexType>
</xs:schema>
 
Basically I have two elements of a complex type that on it=E2=80=99s =
turn has on element of another complex type. It is this last complex =
type that causes the error.. 
Is this normal? What can I do to prevent this kind of situation?
 
Thanks in advance
 
 
 
 
Cl=C3=A1udio Jorge Vieira Teixeira
IEETA-Instituto de Engenharia Electr=C3=B3nica e Telem=C3=A1tica de =
Aveiro
Universidade de Aveiro
Campus Universit=C3=A1rio de Santiago
3810-193 Aveiro
 


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent