Release notes

sql-mirror version 120 new in Alan 2026.3

Switch document

Platform version 2026.3 release notes
Component	Version	Languages
Platform components
model	109	application client_request
interface	20	interface
project-build-environment	45	deployment project_wiring
System types
auto-webclient	athena.2	generator_annotations generator_settings parameters phrases query translations
connector	40	processor template variables
datastore	120	consumed_interfaces_mapping provided_interface_implementation
relational-database-bridge	112	database database_transformation regular_expression_engine
session-manager	35	interface
sql-mirror	120	sql_mapping
webclient	athena.2.0	client bindings default features gui_model handheld features main parameters phrases production features query settings translations views widget

SQL-mirror 120

sql-mirror mapping language: the integer, decimal, date and date-time data type mappings carry a mandatory value range, in raw datastore number values (julian days for date, julian seconds for date-time, the unscaled integer for integer and decimal). A value outside its range is written to the mirror as the range maximum, in both directions, and the mirror reports one line per clamped value on the consultant channel (the os-link error channel in engine mode, stderr in map mode) instead of letting the database refuse the statement. Every mapping file has to be regenerated; generated mappings pick the dialect defaults up automatically.

// old
data-types
	integer: "BIGINT"
	decimal: "DECIMAL"
	date: "DATE"
	date-time: "DATETIME"

// new (MySQL defaults; SQL Server starts its DATETIME range at 204018912000, 1753-01-01)
data-types
	integer: "BIGINT" [ -9223372036854775807 , 9223372036854775807 ]
	decimal: "DECIMAL" [ -9223372036854775807 , 9223372036854775807 ]
	date: "DATE" [ 2086302 , 5373483 ]
	date-time: "DATETIME" [ 180256492800 , 464269017599 ]

Upgrading a mapping from 119.1, 119.2 or partitions-108.1.2. ./alan upgrade runs the transformation for every sql-mirror system; by hand, from the project root, with the old version:

.alan/devenv/system-types/sql-mirror/upgrade/upgrade.sh 119.2 systems/<sys>

The script reads the dialect from the mapping’s identifier-delimiter: line, because the dialect decides the ranges. It rewrites mapping.alan in place, keeping the SQL types that are there and adding the widest range the dialect documents; nothing else in the mapping changes. The bounds are raw datastore values, not SQL literals, so a mirror on a DATETIME2 column, or one that wants a narrower window than its column allows, edits the two numbers afterwards.

A mapping of another dialect, such as PostgreSQL with identifier-delimiter: "\"" "\"", stops the script with cannot infer the dialect, and ./alan upgrade stops at that step. Add the ranges by hand. For PostgreSQL take the years 1 to 9999, which its DATE and TIMESTAMP columns hold:

data-types
	integer: "BIGINT"[ -9223372036854775807 , 9223372036854775807 ]
	decimal: "DECIMAL"[ -9223372036854775807 , 9223372036854775807 ]
	date: "DATE"[ 1721425 , 5373483 ]
	date-time: "TIMESTAMP"[ 148731120000 , 464269017599 ]

Keep the SQL types of the mapping. The failed step wrote nothing, so there is nothing to restore: run ./alan upgrade --retry-interrupted, and the script reports nothing to do for this mapping.