From 78776b6dc3f2138f357c113810c0ff4288fad239 Mon Sep 17 00:00:00 2001 From: Pavel Antoshin Date: Mon, 26 Oct 2026 17:04:50 +0100 Subject: [PATCH 1/2] Mention that Oracle has jvm-dependent locale in date functions --- .../refguide/modeling/domain-model/oql/oql-expression-syntax.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md b/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md index 8bc8214bfc2..f42183e90bb 100644 --- a/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md +++ b/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md @@ -1096,6 +1096,7 @@ When an OQL query is executed, `DATEFORMAT` is converted to the corresponding da 1. Casing (`SUN 3:12 PM` in PostgreSQL, `Sun 3:12 PM` in SQL Server and `Sun 3:12 pm` in HSQLDB) 2. Year formatting (`YY` is formatted as `2026` in MySQL, as `26` in HSQLDB and PostgreSQL, and is not supported at all in SQL Server and SAP HANA). + 3. In Oracle, display language of month and day is tied to the default language of your app. In other databases, it is tied to the database locale. {{% alert color="warning" %}} Always test usages of `DATEFORMAT` with the database engine on which your app runs. OQL queries with `DATEFORMAT` may return different results in HSQLDB and in the production database. From 5c2c751a529b47c187a9a2ed09ae58924cfa479b Mon Sep 17 00:00:00 2001 From: Mark van Ments <35492184+MarkvanMents@users.noreply.github.com> Date: Mon, 2 Nov 2026 15:13:17 +0100 Subject: [PATCH 2/2] Clarify language display behavior in Oracle and other DBs --- .../refguide/modeling/domain-model/oql/oql-expression-syntax.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md b/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md index f42183e90bb..a526899fec3 100644 --- a/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md +++ b/content/en/docs/refguide/modeling/domain-model/oql/oql-expression-syntax.md @@ -1096,7 +1096,7 @@ When an OQL query is executed, `DATEFORMAT` is converted to the corresponding da 1. Casing (`SUN 3:12 PM` in PostgreSQL, `Sun 3:12 PM` in SQL Server and `Sun 3:12 pm` in HSQLDB) 2. Year formatting (`YY` is formatted as `2026` in MySQL, as `26` in HSQLDB and PostgreSQL, and is not supported at all in SQL Server and SAP HANA). - 3. In Oracle, display language of month and day is tied to the default language of your app. In other databases, it is tied to the database locale. + 3. In Oracle, the language in which month and day are displayed is tied to the default language of your app. In other databases, it is tied to the database locale. {{% alert color="warning" %}} Always test usages of `DATEFORMAT` with the database engine on which your app runs. OQL queries with `DATEFORMAT` may return different results in HSQLDB and in the production database.