jOOQ 3.16 has started adding support for spatial extensions in various SQL dialects (#982). This task continues on previous work:

This task collects all related subtasks to add support for SQL spatial extensions of various vendors. This includes:

• Function support (currently taken from PostGIS, see http://postgis.net/workshops/postgis-intro/geometries.html, http://postgis.net/workshops/postgis-intro/postgis-functions.html, check what others exist, and what good names to standardise on)
  • ST_Boundary
    • Not supported in MySQL, Snowflake, SQL Server
  • ST_Covers
    • Not supported in MariaDB, MySQL, SQL Server
  • ST_CoveredBy
    • Not supported in MariaDB, MySQL, SQL Server
  • ST_IsRing
  • ST_IsSimple
    • Not supported in Snowflake, SQL Server
  • ST_IsValid
    • Not supported in MariaDB
  • ST_NPoints (as a parser synonym only for ST_NumPoints, no need to overload in the DSL)
  • ST_Perimeter
    • Not supported in DuckDB, MariaDB, MySQL, Oracle, SQL Server
  • ST_Transform
    • Not supported in DuckDB, MariaDB, SQL Server
  • ST_XMin
    • Not supported in MariaDB, MySQL, SQL Server
  • ST_XMax
    • Not supported in MariaDB, MySQL, SQL Server
  • ST_YMin
    • Not supported in MariaDB, MySQL, SQL Server
  • ST_YMax
    • Not supported in MariaDB, MySQL, SQL Server
  • ST_ZMin
    • Not supported in DuckDB, MariaDB, MySQL, Snowflake, SQL Server
  • ST_ZMax
    • Not supported in DuckDB, MariaDB, MySQL, Snowflake, SQL Server
• Given the big amount of new API, let's revisit splitting up the DSL class: Provide alternative DSL API for DDL statements and some special functions #9321 (this was rejected)
• Dialects improvements
  • Oracle
    • Support Oracle ST_GEOMETRY vs SDO_GEOMETRY: https://docs.oracle.com/database/121/SPATL/st_geometry-and-sdo_geometry-interoperability.htm#SPATL563
• New dialects support
  • DuckDB
  • Oracle improvements: Correctly implement numerous Oracle specific ST_Geometry spatial functions #16844

To be continued:

• Continue support for spatial extensions #17494