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 enginesEngineering1 min read

The XML SQL dialect grows: UNION, several CTEs, synonyms, DECODE, text search

The engine-neutral query dialect gains UNION with ordering, several common table expressions per query, synonyms, CROSS JOIN and nested joins, a rowid column, DECODE, an include resolver and full-text search.

A dialect that compiles to seven engines earns its keep by covering what application developers actually write. This release closed a set of gaps that had each been forcing a native-SQL escape hatch.

Query constructs

  • UNION with a type attribute and an ORDER BY over the union.
  • Several CTEs in one query, and multiset columns.
  • Joins CROSS JOIN and nested joins.
  • Rowid and DECODE A rowid column element, and DECODE compiled to each engine's form.
  • Include An include resolver lets a query fragment be shared.

Schema and search

  • Synonyms CREATE SYNONYM in the schema model.
  • Full-text search A contains function backed by an Informix BTS index, with tag and attribute indexing options, and by a SQL Server full-text index created with the system stop list.

Full-text search was later generalised to six engines with a capability descriptor per engine. This release is where the dialect first learned it.

On the platformDataPlatform

All posts