Export (0) Print
Expand All
Expand Minimize

XSD Annotations (SQLXML 4.0)

The following table lists the XSD annotations that were introduced in SQL Server 2005, and compares them with the XDR annotations that were introduced in SQL Server 2000.

XSD annotation

Description

Topic link

XDR annotation

sql:encode

When an XML element or attribute is mapped to a SQL Server BLOB column, allows requesting a reference URI. This URI can be used later to return BLOB data.

Requesting URL References to BLOB Data Using sql:encode (SQLXML 4.0)

url-encode

sql:guid

Allows you to specify whether to use a GUID value generated by SQL Server or use the value provided in the updategram for that column.

Using the sql:identity and sql:guid Annotations

Not supported

sql:hide

Hides the element or attribute that is specified in the schema in the resulting XML document.

Hiding Elements and Attributes by Using sql:hide

Not supported

sql:identity

Can be specified on any node that maps to an IDENTITY-type database column. The value specified for this annotation defines how the corresponding IDENTITY-type column in the database is updated.

Using the sql:identity and sql:guid Annotations

Not supported

sql:inverse

Instructs the updategram logic to inverse its interpretation of the parent-child relationship that has been specified using <sql:relationship>.

Specifying the sql:inverse Attribute on sql:relationship (SQLXML 4.0)

Not supported

sql:is-constant

Creates an XML element that does not map to any table. The element appears in the query output.

Creating Constant Elements Using sql:is-constant (SQLXML 4.0)

Same

sql:key-fields

Allows specification of column(s) that uniquely identify the rows in a table.

Identifying Key Columns Using sql:key-fields (SQLXML 4.0)

Same

sql:limit-field

sql:limit-value

Allows limiting the values that are returned on the basis of a limiting value.

Filtering Values Using sql:limit-field and sql:limit-value (SQLXML 4.0)

Same

sql:mapped

Allows schema items to be excluded from the result.

Excluding Schema Elements from the Resulting XML Document Using sql:mapped (SQLXML 4.0)

map-field

sql:max-depth

Allows you to specify depth in recursive relationships that are specified in the schema.

Specifying Depth in Recursive Relationships by Using sql:max-depth

Not supported

sql:overflow-field

Identifies the database column that contains the overflow data.

Retrieving Unconsumed Data Using the sql:overflow-field (SQLXML 4.0)

Same

sql:prefix

Creates valid XML ID, IDREF, and IDREFS. Prepends the values of ID, IDREF, and IDREFS with a string.

Creating Valid ID, IDREF, and IDREFS Type Attributes Using sql:prefix (SQLXML 4.0)

Same

sql:relationship

Specifies relationships between XML elements. The parent, child, parent-key, and child-key attributes are used to establish the relationship.

Specifying Relationships Using sql:relationship (SQLXML 4.0)

The attribute names are different:

key-relation

foreign-relation

key

foreign-key

sql:use-cdata

Allows specifying CDATA sections to be used for certain elements in the XML document.

Creating CDATA Sections Using sql:use-cdata (SQLXML 4.0)

Same

Note Note

The XSD native targetNamespace attribute replaces the target-namespace annotation that was introduced in the SQL Server 2000 XDR mapping schema.

Community Additions

ADD
Show:
© 2014 Microsoft