Data type support
HCL OneTest™ API 8.0.1 or later supports most built-in data types of supported database management systems. HCL OneTest™ API 8.5.1 or later supports certain user-defined types of some supported database management systems.
A user-defined type (UDT) is a named data type that is created in a database by a user.
The following table lists the database management systems supported by HCL OneTest™ API and indicates the level, if any, of UDT functionality of each database that is supported by different versions of HCL OneTest™ API.
Database management system (DBMS) | DBMS UDT support (level) | UDT support (level) for versions of HCL OneTest™ API earlier than 8.5.1 | HCL OneTest™ API 8.5.1 or later UDT support (level) |
---|---|---|---|
IBM® Db2® |
Yes (simple and complex) |
No |
Yes (simple only) |
Microsoft™ SQL Server |
Yes (simple and complex) |
No |
Yes (simple only) |
MySQL |
No |
(Not applicable) |
(Not applicable) |
Oracle |
Yes (complex only) |
No |
No |
Specifically, 8.5.1 or later supports UDTs as data types of table columns and in stored procedures that map to a single built-in data type in Db2® for Linux™, UNIX™, and Windows™, Db2® for z/OS®, and Microsoft™ SQL Server.
When 8.5.1 or later processes a table in a "live" (production) database that has complex UDTs or processes a stored procedure that has input and output parameters of UDTs, HCL OneTest™ API does not create UDTs in the simulation database. Instead, HCL OneTest™ API resolves a UDT in the live database to its built-in data type (that is, the source) and uses that built-in data type in the simulation database.
The TIMESTAMP type in Oracle is not supported by Apache Derby when using the integrated simulation database. Hence, when you record Oracle TIMESTAMP values, no rows are inserted into the database stub. To work around this problem, you must use a separate Oracle schema for the database stub.