Built-in Types

The following built-in types are provided:

CDS Type	Arguments / Remarks	Example Value	SQL ⁽⁶⁾
`UUID`	an opaque 36-characters string ⁽¹⁾	`'be071623-8699-4106-b6fa-8e3cb04c261e'`	NVARCHAR(36)
`Boolean`		`true`	BOOLEAN
`UInt8`	⁽²⁾	`133`	TINYINT
`Int16`		`1337`	SMALLINT
`Int32`		`1337`	INTEGER
`Integer`		`1337`	INTEGER
`Int64`		`1337`	BIGINT
`Integer64`		`1337`	BIGINT
`Decimal`	( `precision`, `scale` ) ⁽³⁾	`15.2`	DECIMAL
`Double`		`15.2`	DOUBLE
`Date`		`'2021-06-27'`	DATE
`Time`		`'07:59:59'`	TIME
`DateTime`	sec precision	`'2021-06-27T14:52:23Z'`	TIMESTAMP
`Timestamp`	0.1 µs precision ⁽⁴⁾	`'2021-06-27T14:52:23.123Z'`	TIMESTAMP
`String`	( `length` ) ⁽⁵⁾	`'hello world'`	NVARCHAR
`Binary`	( `length` ) ⁽⁵⁾		VARBINARY
`LargeBinary`			BLOB
`LargeString`		`'hello world'`	NCLOB

Remarks

⁽¹⁾ At runtime, UUIDs are treated as opaque values and are, for example, not converted to lower case on input. UUIDs generated in the application are RFC 4122-compliant. See Don’t Interpret UUIDs! for details.

⁽²⁾ Not supported on PostgreSQL, as there is no TINYINT. Not supported on H2, as TINYINT is signed on H2. Use Int16 instead.

⁽³⁾ Arguments precision and scale are optional → if omitted a decfloat type is used

⁽⁴⁾ Up to 7 digits of fractional seconds; if a data is given with higher precision truncation may occur

⁽⁵⁾ Argument length is optional → use options cds.cdsc.defaultStringLength and cds.cdsc.defaultBinaryLength to control the project-specific default length used for OData and SQL backends. If not set, the global default length 5000 is used for SQL backends.

⁽⁶⁾ Mapping to ANSI SQL types are given for comparison. Note though, that you need to have the specification of your target database in mind when considering, for example, length restrictions.

Keyboard Shortcuts

Built-in Types

Remarks

See also…