Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Uniqueness and case sensitivity

From: Xan Gregg <xan.gregg@---.--->
To: Jeff Dahl <jddahl@------.--->
Date: 4/12/2004 6:25:00 AM
I missed that your two questions were of opposite polarity.

>>> Shouldn't unique be case-sensitive?

Yes, because of the material your cited earlier.

>>> Given the following XML segment:
>>>
>>> <foos>
>>>    <foo id="1490" name="myName"/>
>>>    <foo id="9091" name="myNAME"/>
>>> </foos>
>>>
>>> shouldn't a uniqueness constraint ... throw an error?

No, because unique is case-sensitive, and so 'myName' and 'myNAME' are 
different.

xan


>> Yes, and I don't see any other problems with your example.  Are you 
>> sure your processor enforces identity constraints?
>
> Using the sample program, sax.Counter, of Xerces 2.6.2 with the flags, 
> -v -s -f -np, will throw:
> 'Duplicate unique value [myNAME] declared for identity constraint of 
> element "foos".'
> when the case is the same.

From kal@t...  Tue Apr 13 05:01:13 2004
Return-


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