ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →
Data and enginesProduct Release1 min read

Geometry functions in the engine-neutral SQL dialect, on six engines

Twelve spatial functions, from constructing points and polygons to area, buffer, intersection, length and centroid, compile to Informix, Oracle, PostgreSQL, SQL Server, DB2 and MySQL from one dialect.

Logistics, field service and retail planning all ask spatial questions: which depots lie within a radius, how long is a route, where is the centre of a territory. This release adds a spatial vocabulary to the engine-neutral dialect so those questions are written once.

The functions

  • Construction Point, polygon, line and generic geometry from well-known text, and back to text.
  • Measurement Area, length, number of points.
  • Derivation Buffer, intersection, centroid, envelope.
  • Six engines Each function compiles to the native spatial call on Informix, Oracle, PostgreSQL, SQL Server and DB2, with MySQL added in this release.

Scale, rotate and translate helpers are documented in the abstract model for the engines that expose them.

On the platformDataPlatform

All posts