Subject:Re: KEYS (and UNIQUE) enforced? Author:Alberto Massari Date:11 Feb 2002 06:11 AM
At 17.18 09/02/2002 -0500, you wrote:
>From: "Bruce Wallace"
>build 69k doesnt seem to enforce KEY uniqueness when validating my XML
>against my Schema.
>Doesnt your validator do this yet?
>(see attached if it supposedly does).
Xerces does support enforcement of the key/keyref/unique definitions (even
if they warn their interpretation of the specs regarding keyref could be
non-standard - see http://xml.apache.org/xerces-c/schema.html for details).
The problem with your schema is that you have:
But the XPath expression "product" will never be true, as the only child of
products_by_vendor is "vendor". If you change the xs:selector definition to
use "vendor/product", you will get two uniqueness errors.
However, your schema doesn't store the "product" elements just as direct
child of a "vendor", but also as part of a "suite"; so an xs:key structure
using the XPath expression "vendor/product" will not check for duplicate
products stored inside the suite. So, if what you want is to enforce that
no duplicate product IDs are present in the entire document you should use