From 623d33b9ee8cc96236e4ef9b2c168552034fe5bf Mon Sep 17 00:00:00 2001 From: Bas de Bakker Date: Thu, 10 Sep 2026 13:38:38 +0200 Subject: [PATCH 1/2] Explain new SAP HANA driver situation --- .../en/docs/refguide/runtime/data-storage/saphana.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/content/en/docs/refguide/runtime/data-storage/saphana.md b/content/en/docs/refguide/runtime/data-storage/saphana.md index ab8689f3619..79799e637bb 100644 --- a/content/en/docs/refguide/runtime/data-storage/saphana.md +++ b/content/en/docs/refguide/runtime/data-storage/saphana.md @@ -8,6 +8,18 @@ weight: 70 The behavior of Mendix using an SAP HANA database has some minor differences when compared with using a PostgreSQL database. These differences are documented below. +## SAP HANA JDBC driver + +Starting with Mendix version 11.15.0 and 11.12.5, we no longer distribute the SAP HANA JDBC driver with Studio Pro, because of licensing issues. + +If you deploy your app to [SAP BTP using the Mendix Portal](/developerportal/deploy/sap-cloud-platform/), the driver will be added to your app during deployment. No special treatment is necessary. + +If you want to test your app locally against a SAP HANA database or deploy it using your own infrastructure, you will need to add the JDBC driver to your app like any other 3rd party jar file using one of these two methods: +* Download the SAP HANA JDBC driver manually from [Maven Central](https://central.sonatype.com/artifact/com.sap.cloud.db.jdbc/ngdbc) and add it to the `userlib` folder in your app. +* Use [Managed Dependencies](/refguide/managed-dependencies/) to add a dependency with Group ID `com.sap.cloud.db.jdbc` and Artifact ID `ngdbc`. This adds the driver to the `vendorlib` folder in your app. + +We recommend using the latest driver version that has major version 2. + ## Behavior of Unlimited and Very Long Strings ### Comparison Functions From 5e05285cefbea03df04daab9515944f080c8869c Mon Sep 17 00:00:00 2001 From: MarkvanMents Date: Mon, 21 Sep 2026 14:01:33 +0200 Subject: [PATCH 2/2] Proofread SAP Hana JDBC Driver update --- .vale/styles/Mendix/Acronyms.yml | 6 ++++++ .../docs/refguide/runtime/data-storage/saphana.md | 13 +++++++------ 2 files changed, 13 insertions(+), 6 deletions(-) diff --git a/.vale/styles/Mendix/Acronyms.yml b/.vale/styles/Mendix/Acronyms.yml index 27d4f079028..d4a7e887de5 100644 --- a/.vale/styles/Mendix/Acronyms.yml +++ b/.vale/styles/Mendix/Acronyms.yml @@ -11,6 +11,7 @@ scope: - blockquote # Ensures that the existence of 'first' implies the existence of 'second'. # Known issue: Doesn't recognize hyperlinks for acronym definitions +# Known issue: Doesn't recognize CLOB (Character Large Object) always expects definition first—"Character Large Object (CLOB)" even if acronym is more common than definition # Modified from Microsoft.Acronyms to accept sentence-case definitions (e.g., "personal access token (PAT)" not just "Personal Access Token (PAT)") first: '\b([A-Z]{3,5})\b' second: '(?:\b[A-Za-z][a-z]+ )+\(([A-Z]{3,5})\)' @@ -18,6 +19,7 @@ second: '(?:\b[A-Za-z][a-z]+ )+\(([A-Z]{3,5})\)' exceptions: - API - ASP + - BTP - CLI - CPU - CSS @@ -33,19 +35,23 @@ exceptions: - GPU - GTK - GUI + - HANA - HTML - HTTP - HTTPS - IDE - JAR + - JDBC - JPEG - JPG - JSON - JSX - LESS - LLDB + - LTS - MDA - MPR + - MTS - NET - NOTE - NVDA diff --git a/content/en/docs/refguide/runtime/data-storage/saphana.md b/content/en/docs/refguide/runtime/data-storage/saphana.md index 79799e637bb..816636ccf45 100644 --- a/content/en/docs/refguide/runtime/data-storage/saphana.md +++ b/content/en/docs/refguide/runtime/data-storage/saphana.md @@ -8,17 +8,18 @@ weight: 70 The behavior of Mendix using an SAP HANA database has some minor differences when compared with using a PostgreSQL database. These differences are documented below. -## SAP HANA JDBC driver +## Adding SAP HANA JDBC Driver -Starting with Mendix version 11.15.0 and 11.12.5, we no longer distribute the SAP HANA JDBC driver with Studio Pro, because of licensing issues. +Mendix Studio Pro versions 11.15.0 and above, and Mendix Studio Pro version 11.12 ([LTS](/releasenotes/studio-pro/lts-mts/)) patch versions 11.12.5 and above, no longer include the SAP HANA JDBC driver. This is because of licensing issues. -If you deploy your app to [SAP BTP using the Mendix Portal](/developerportal/deploy/sap-cloud-platform/), the driver will be added to your app during deployment. No special treatment is necessary. +If you deploy your app to SAP BTP using the [Mendix Portal](/developerportal/deploy/sap-cloud-platform/), the driver will be added to your app during deployment. You do not have to take any additional steps. + +If you want to test your app locally against a SAP HANA database or deploy it using your own infrastructure, you must add the JDBC driver to your app like any other 3rd party jar file using one of the following two methods: -If you want to test your app locally against a SAP HANA database or deploy it using your own infrastructure, you will need to add the JDBC driver to your app like any other 3rd party jar file using one of these two methods: * Download the SAP HANA JDBC driver manually from [Maven Central](https://central.sonatype.com/artifact/com.sap.cloud.db.jdbc/ngdbc) and add it to the `userlib` folder in your app. * Use [Managed Dependencies](/refguide/managed-dependencies/) to add a dependency with Group ID `com.sap.cloud.db.jdbc` and Artifact ID `ngdbc`. This adds the driver to the `vendorlib` folder in your app. -We recommend using the latest driver version that has major version 2. +Mendix recommends using the latest driver version that has major version 2. ## Behavior of Unlimited and Very Long Strings @@ -30,7 +31,7 @@ See also [Case-Sensitive Database Behavior](/refguide/case-sensitive-database-be ### Sorting, Grouping, and Aggregating -It is not possible to sort, group, or use aggregate functions such as `count()` on unlimited strings or strings with a specified length greater than 5000 characters. This is because such long or unlimited strings are implemented with the data type CLOB. Consider decreasing the length of the string attribute or removing it from data grids. +You cannot sort, group, or use aggregate functions such as `count()` on unlimited strings or strings with a specified length greater than 5000 characters. This is because such long or unlimited strings are implemented with the data type CLOB (Character Large Object). Consider decreasing the length of the string attribute or removing it from data grids. ### Selecting DISTINCT Attribute