A parser is supplied for the body of a message in the MRM domain;
it associates each field with a specific data type.
The following table
shows the mapping from XML Schema data types that you have specified for elements
in the MRM to data types used by the broker and supported by ESQL. When you
create an element, you might find that associated value constraints are created
to ensure a more accurate mapping of the XML Schema type.
Data type of the element |
Represented as |
ANYURI |
STRING |
BASE64BIN |
BINARY |
BOOLEAN |
BOOLEAN |
BYTE |
INTEGER |
DATE |
DATETIME |
DATETIME |
DATETIME |
DECIMAL |
DECIMAL |
DOUBLE |
FLOAT |
DURATION |
STRING |
ENTITIES |
STRING |
ENTITY |
STRING |
FLOAT |
FLOAT |
GDAY |
DATETIME |
GMONTH |
DATETIME |
GMONTHDAY |
DATETIME |
GYEAR |
DATETIME |
GYEARMONTH |
DATETIME |
HEXBINARY |
BINARY |
ID |
STRING |
IDREF |
STRING |
IDREFS |
STRING |
INT |
INTEGER |
INTEGER |
DECIMAL |
LANGUAGE |
STRING |
LONG |
INTEGER |
NAME |
STRING |
NCNAME |
STRING |
NEGATIVE_INTEGER |
DECIMAL |
NMTOKEN |
STRING |
NMTOKENS |
STRING |
NON_NEGATIVE_INT |
DECIMAL |
NON_POSITIVE_INTEGER |
DECIMAL |
NORMAILIZED_STRING |
STRING |
NOTATION |
STRING |
POSITIVE_INTEGER |
DECIMAL |
QNAME |
STRING |
SHORT |
INTEGER |
STRING |
STRING |
TIME |
DATETIME |
TOKEN |
STRING |
UNSIGNED_BYTE |
INTEGER |
UNSIGNEDINT |
INTEGER |
UNSIGNEDLONG |
INTEGER |
UNSIGNED_SHORT |
INTEGER |