The DataBlade API provides the following data types to support varying-length data.
| DataBlade API Data Type | SQL
Varying-Length
Data Type |
More Information |
|---|---|---|
| mi_lvarchar | LVARCHAR | The mi_lvarchar Data Type |
| mi_bitvarying | BITVARYING | The mi_bitvarying Data Type |
| mi_sendrecv | SENDRECV | Send and Receive Support Functions |
| mi_impexp | IMPEXP | External Unload Representation |
| mi_impexpbin | IMPEXPBIN | Internal Unload Representation |
All these DataBlade API data types have the same underlying structure. For more information about the structure of a varying-length data type, see Creating a Varying-Length Structure.
These varying-length data types (mi_lvarchar, mi_bitvarying, mi_sendrecv, mi_impexp, mi_impexpbin, and varying-length opaque types) cannot fit into an MI_DATUM structure. Therefore, they must be passed by reference to and from C UDRs.
All data types, including mi_lvarchar, must be passed by reference within client LIBMI applications.