Pitney Bowes MapInfo Professional - Manual (Page 176)

Oracle Data Support
Working with Oracle Spatial Data
MapInfo Professional uses Oracle Spatial for Oracle tables (XY is supported via OCI). MapInfo
Professional does not support HH_CODE (and the old version of SDO index types).
Supported Oracle Data Types
The following lists non-spatial data types from Oracle Spatial and what they are treated as in MapInfo
Professional:
to MapInfo Professional From Oracle
BinaryString up to 127 bytes shown as Hex
characters RAW, LONG RAW
MIObject Named type
MIObject Named Object type (SDO_GEOM)
Not Supported BLOB, CLOB
Character CHAR, VARCHAR, LONG, LONG VARCHAR
if no scale or precision: Float else Decimal Number, Decimal
Integer INTEGER
Float FLOAT
Date DATE
MapInfo Professional captures many Oracle data types and translates them into MapInfo native types.
When the column is updated, Oracle data makes sure that the data being bound is translated into the
column format (for example, MapInfo Professional can bind a character as a long and send it through
to Oracle and on the other end it will be translated into a long number in the table).
Spatial Object Types from Oracle Spatial to MapInfo Professional
to MapInfo Professional From Oracle: GTYPES
NULL 0 UNKNOWN_GEOMETRY (Spatial ignores this
geometry.)
Point 1 POINT Geometry contains one point.
Line (if only 2 pts) or Polyline if > 2 pts) 2 LINESTRING Geometry contains one line string.
Region 3 POLYGON Geometry contains one polygon.
Collection 4 Collection Geometry is a heterogeneous
collection of elements.
MultiPoint 5 MULTIPOINT Geometry has multiple points.
Region 6 MULTILINESTRING Geometry has multiple line
strings. Poly-line
MapInfo Professional 12.5 176
About Supported DBMS Data Types