How is ST_Geometry implemented?
ST_Geometry is implemented as a user-defined type. ArcSDE geodatabase storage for Oracle, IBM DB2, IBM Informix, and PostgreSQL use the ST_Geometry spatial type, which can be used in the geodatabase as well as accessed using SQL. This allows you to write SQL applications using your database management system (DBMS) that can access and use feature operations and queries.
In DB2 and Informix, an additional spatial module is required to use ST_Geometry in the database.
Each DBMS supports ST_Geometry as follows:
DBMS |
Description |
---|---|
Oracle |
The ST_Geometry data type is one of the options for storing feature geometry in an ArcSDE geodatabase. It is included with ArcSDE for Oracle and is one of the feature storage options you have for Oracle. It is a high-performance storage type provided as part of ArcSDE for Oracle that includes ISO- and OGC-compliant SQL access to geodatabase features. |
IBM DB2 |
The DB2 Spatial Extender provided by IBM as part of the DB2 product is the only option used to store feature geometry in geodatabases in DB2. It was codeveloped by ESRI and IBM and is a high-performance storage type that provides ISO- and OGC-compliant SQL access to geodatabase features. Note: There are some differences in SQL syntax between DB2 for z/OS and DB2 for Windows/Linux/UNIX. Consult the DB2 documentation for proper syntax for the DBMS version you are using. |
IBM Informix |
The Informix Spatial DataBlade provided by IBM as part of the Informix product is the only option used to store feature geometry in geodatabases in Informix. It was codeveloped by ESRI and IBM and is a high-performance storage type that provides ISO- and OGC-compliant SQL access to geodatabase features. |
PostgreSQL |
The ST_Geometry data type is the default for storing feature geometry in an ArcSDE geodatabase in PostgreSQL. As with the other DBMS implementations, the PostgreSQL implementation provides ISO- and OGC-compliant SQL access to geodatabase features. |
For information on the ST_Geometry in each database, see the following topics: