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

Regular expressions, window functions, else-if and EXPLAIN in the XML dialect

Regular-expression match, extract and split compile per engine, with ratio-to-report, NTILE, octet length and hex conversions. Conditions gain else-if, foreign keys gain deferrability, plans are read.

The engine-neutral dialect grows by the functions application developers reach for and find missing. This release adds a set that had each been forcing native SQL.

Functions

  • Regular expressions Match, extract and split compile to each engine's form: the native regexp functions on most, function calls on Informix, the match and extract functions on ClickHouse, CASE wrappers on Oracle and HANA. Engines without support are excluded per function rather than failing at run time.
  • Analytics Ratio to report, native on Oracle and Informix and a window expression elsewhere; NTILE with partitioning.
  • Bytes and hex Octet length tested across twelve drivers, hex to integer and back, and a bitwise XOR aggregate.

Grammar and schema

  • Else-if A condition gains then, else-if and else, evaluated in document order, backwards compatible.
  • Deferrable foreign keys A deferrability attribute, immediate or deferred, with PostgreSQL and Oracle tests proving statement-level against commit-level violation.
  • EXPLAIN An explain element reads execution plans alongside the DDL.

Each addition is one XML element and a test per engine. That is the cost of a dialect that stays honest.

On the platformDataPlatform

All posts