I have a schema that allows the following XML.

<Data>
<Country>1150</Country>
<Hypertension>
<HypertensionSince>1995</HypertensionSince>
<HypertensionTreated>0</HypertensionTreated>
</Hypertension>
<Diabetes/>
</Data>

In the sql server, we have one table. In the XSD the
elements Hypertension and Diabetes are declared as followed:
<xs:element name="Hypertension"
type="basic:HypertensionType"
minOccurs="0" sql:relationship="XBS-XBS"
sql:relation="XBS_ExchangeBasis"/>

<xs:element name="Diabetes" type="basiciabetesType" minOccurs="0"
sql:relationship="XBS-XBS" sql:relation="XBS_ExchangeBasis"/>

So there is a selfjoin since all Data is stored in one table.

The problem is, when there are only null values for example the
diabetes fields then only an empty tag is created. I would like to
have no tag at all to be created when there is no data. At least the
child element for diabetes are not created since there is no data. But
how to avoid the creation of the empty parent tag?

Hope someone can help me out.

Greetings
Mike

"MIchael Bals" <Michael.Bals (AT) web (DOT) de> wrote

[snip]
I think this is a problem with the current release and I don't believe there
is a fix for it.

--
Bryant

If you map a row that contains only NULL fields, then there exists a row
without properties and we map it (correctly in my opinion) to an element
that represents the present row without subelements or attributes.

If you do not want to have this appear, define a view that filters such rows
and map against the view.

I hope this helps.
Michael

"Bryant Likes" <bryant (AT) suespammers (DOT) org> wrote