Geospatial types (ST_Geometry, MBR, and so on) are supported by the ODBC driver in a transparent manner by making us of the import/export transform functionality of the Teradata Database. For example, a value of type ST_Geometry is imported/exported as a CLOB and a value of type MBR as a VARCHAR (256). Please refer to Teradata Database, SQL Geospatial Types (B035-1181), for more information about the transform types for the different Geospatial types.
An ODBC application sees the Geospatial types in the database as the standard SQL types SQL_LONGVARCHAR or SQL_VARCHAR depending on the database transform type. Values of the Geospatial types are transformed by the database to or from values of these standard SQL types. All the syntax for types, methods, functions, and expressions as used for Geospatial fall within the standard SQL syntax.
The specific Geospatial type behind the database transform type can be obtained through the SQL_DESC_TD_UDT_NAME descriptor field, which returns the fully qualified name of the Geospatial type. Please refer to “SQL_DESC_TD_UDT_NAME” on page 116 for more information.
Note: Large object (LOB) support should not be disabled when using Geospatial data types. LOB support is enabled by default and the option to disable LOB support is deprecated.