Stored procedures are where database portability usually dies: each engine has its own procedural dialect. The platform's procedure language is written once in XML and compiled to each engine's native form. This release widened what it can express.
Compiled to seven engines
- Triggers The procedure model compiles triggers for Informix, Oracle, HANA, PostgreSQL, MySQL, SQL Server and DB2.
- FOR IN loops One loop form becomes FOR IN on Informix, a loop over a collection table on Oracle, FOREACH over an array on PostgreSQL, and plain loops on MySQL and SQL Server.
- Common table expressions WITH inside a procedure, with a not-found check, across DB2, H2, HANA, Informix, MySQL, Oracle and PostgreSQL.
- Dynamic SQL EXECUTE IMMEDIATE, execute-function and execute-procedure statements, and dynamic SQL with a cursor over its result. UNION inside procedures.
Where an engine says no
- Recorded, not hidden SQL Server forbids dynamic SQL inside functions, and MySQL forbids it in functions and triggers. The compiler records the limit rather than emitting code that fails at deploy time.
A later release added exception handling, set operators, locking and DDL to the same language. The principle is the same: write the logic once, let the compiler argue with each engine.