An application written against the platform's engine-neutral dialect runs on whichever database the customer has. This release adds SAP HANA, the engine most often found beside an SAP estate, and teaches the dialect the constructs HANA does differently.
HANA
- Triggers Before and after triggers compile to HANA, alongside Informix and Oracle.
- Hierarchies A hierarchy element emits START WITH and CONNECT BY PRIOR on HANA and Oracle, and a recursive common table expression on engines without it.
- Column tables A table type attribute creates a column-store table on HANA; the same attribute creates an unlogged table on PostgreSQL.
- Types mapped Small date, timestamp and money types map onto their HANA equivalents.
Around it
- Hive The Hive JDBC driver ships as a bundle with its own connection implementation and test pool.
- Server-level connections declared Drivers that cannot open a connection at server level, such as DB2, Derby and H2, say so, and the platform routes administrative work accordingly.
- A driver catalogue JDBC driver information is catalogued in the configuration database.
Engine coverage is a long-term commitment rather than a feature: every later dialect addition, from regular expressions to geometry, is tested against this list.