From ea09f0d44964f50a8f91ce5b40739fec494dd84c Mon Sep 17 00:00:00 2001 From: Augusto Passalacqua Date: Mon, 22 Sep 2025 14:02:30 +0200 Subject: [PATCH 1/7] Add warnings about the performance impact of DataStorage_QueryPlan --- .../entities/view-entities/use-view-entities.md | 6 +++++- .../entities/view-entities/use-view-entities.md | 6 +++++- content/en/docs/refguide10/runtime/logging/_index.md | 2 +- content/en/docs/refguide8/runtime/logging.md | 2 +- content/en/docs/refguide9/runtime/logging.md | 2 +- 5 files changed, 13 insertions(+), 5 deletions(-) diff --git a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md index b5d64cd32d2..524c3184e1a 100644 --- a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md +++ b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md @@ -173,7 +173,11 @@ The database follows the below process: Even though the query is using a view that also includes address information, the database ignores this information, as it is not relevant when counting customers by age. -If you set the `DataStorage_QueryPlan` log node to Trace, you see the query plan for your queries in the Mendix Runtime log. +If you set the `DataStorage_QueryPlan` log node to Trace, you see the query plan for your all your queries in the Mendix Runtime log. + +{{% alert color="warning" %}} +The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production. +{{% /alert %}} ## Read More diff --git a/content/en/docs/refguide10/modeling/domain-model/entities/view-entities/use-view-entities.md b/content/en/docs/refguide10/modeling/domain-model/entities/view-entities/use-view-entities.md index 38f0d21da7d..b9d8ddb27a1 100644 --- a/content/en/docs/refguide10/modeling/domain-model/entities/view-entities/use-view-entities.md +++ b/content/en/docs/refguide10/modeling/domain-model/entities/view-entities/use-view-entities.md @@ -124,7 +124,11 @@ The database follows the below process: Even though the query is using a view that also includes address information, the database ignores this information, as it is not relevant when counting customers by age. -If you set the `DataStorage_QueryPlan` log node to Trace, you see the query plan for your queries in the Mendix Runtime log. +If you set the `DataStorage_QueryPlan` log node to Trace, you see the query plan for all your queries in the Mendix Runtime log. + +{{% alert color="warning" %}} +The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production. +{{% /alert %}} ## Read More diff --git a/content/en/docs/refguide10/runtime/logging/_index.md b/content/en/docs/refguide10/runtime/logging/_index.md index 323d589f59f..476719454b0 100644 --- a/content/en/docs/refguide10/runtime/logging/_index.md +++ b/content/en/docs/refguide10/runtime/logging/_index.md @@ -64,7 +64,7 @@ This list is currently incomplete and is being updated. | Connector | Logs when standard or custom request handlers (added through Core#addRequestHandler) are registered, or when a path is called that does not have a registered request handler. | | Core | Logs messages from the core runtime. This can be startup of the runtime, version of the runtime, license being used and issues related to interpreting the model. | | DataStorage_QueryHandling | Logs messages related to the queries that are being executed. | -| DataStorage_QueryPlan | Query execution plan information for installations (currently only supported for PostgreSQL databases). | +| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production.{{% /alert %}} | | DocumentExporter | Logs messages related to the templating engine that generates documents. | | FileDocumentSizesPopulateJob | Logs messages for a background job that populates the file-size field in the database for documents that do not have that field filled (used during legacy migration). | | InvalidRequestLimiter | Logs messages related to responses being throttled due to invalid requests. | diff --git a/content/en/docs/refguide8/runtime/logging.md b/content/en/docs/refguide8/runtime/logging.md index a15fabaefaa..4f48dbe7231 100644 --- a/content/en/docs/refguide8/runtime/logging.md +++ b/content/en/docs/refguide8/runtime/logging.md @@ -61,7 +61,7 @@ This list is currently incomplete and is being worked on. | Connector | | | Core | Logs messages from the core runtime. This can be startup of the runtime, version of the runtime, license being used and issues related to interpreting the model. | | DataStorage_QueryHandling | Logs messages related to the queries that are being executed. | -| DataStorage_QueryPlan | Query execution plan information for installations (currently only supported for PostgreSQL databases). | +| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production.{{% /alert %}} | DocumentExporter | Logs messages related to the templating engine that generates documents. | | FileDocumentSizesPopulateJob | Logs messages for a background job that populates the file-size field in the database for documents that do not have that field filled (used during legacy migration). | | I18NProcessor | Logs messages related to translation of the app. | diff --git a/content/en/docs/refguide9/runtime/logging.md b/content/en/docs/refguide9/runtime/logging.md index 9e3732db07b..92b23eafc4e 100644 --- a/content/en/docs/refguide9/runtime/logging.md +++ b/content/en/docs/refguide9/runtime/logging.md @@ -64,7 +64,7 @@ This list is currently incomplete and is being updated. | Connector | | | Core | Logs messages from the core runtime. This can be startup of the runtime, version of the runtime, license being used and issues related to interpreting the model. | | DataStorage_QueryHandling | Logs messages related to the queries that are being executed. | -| DataStorage_QueryPlan | Query execution plan information for installations (currently only supported for PostgreSQL databases). | +| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production.{{% /alert %}} | DocumentExporter | Logs messages related to the templating engine that generates documents. | | FileDocumentSizesPopulateJob | Logs messages for a background job that populates the file-size field in the database for documents that do not have that field filled (used during legacy migration). | | IDResolution | Information on retrieval queries and runtime operations that are being executed. | From 2b735fa021cd3e8fd6282c27818c54e2d0c1e84d Mon Sep 17 00:00:00 2001 From: Augusto Passalacqua Date: Mon, 22 Sep 2025 14:34:34 +0200 Subject: [PATCH 2/7] Do not claim JdbcUrl overrides database name in all cases --- content/en/docs/refguide/runtime/custom-settings/_index.md | 4 ++-- content/en/docs/refguide10/runtime/custom-settings/_index.md | 4 ++-- content/en/docs/refguide9/runtime/custom-settings/_index.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/refguide/runtime/custom-settings/_index.md b/content/en/docs/refguide/runtime/custom-settings/_index.md index d82f2cb43ff..3aa6f53f200 100644 --- a/content/en/docs/refguide/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide/runtime/custom-settings/_index.md @@ -124,8 +124,8 @@ The settings below influence the behavior of the log files. These settings can o | DatabaseType | Defines the database engine which is used as the Mendix database. Valid values are `HSQLDB`, `MYSQL`, `ORACLE`, `POSTGRESQL`, `SAPHANA`, and `SQLSERVER`. | | | DatabaseUserName | Name required for authentication to the database. | | | DatabasePassword | Password for the `DatabaseUserName` supplied above. | | -| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). | | -| DatabaseName | The name of the database or schema used by the Mendix app
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). | | +| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). +| DatabaseName | The name of the database or schema used by the Mendix app
Depending on the database type, it is required even if a `DatabaseJdbcUrl` is defined. | | | DatabaseJdbcUrl | Defines the JDBC URL to use for the database connection (which overrides the other database connection settings). | | | DatabaseUseSsl | When `true`, the connection will be made using SSL without certificate validation. If you need certificate validation, use [DatabaseJdbcUrl](#DatabaseJdbcUrl) instead.
When `false`, the connection will be made without SSL (this is only relevant for SQL Server, which uses SSL by default). | | | DatabaseUseIntegratedSecurity | This setting defines whether integrated security will be used to authenticate to SQL Server. If true, user name and password will not be used.
Ensure that the proper domain user for accessing the SQL Server is authenticated on the runtime server using the `kinit` command. | false | diff --git a/content/en/docs/refguide10/runtime/custom-settings/_index.md b/content/en/docs/refguide10/runtime/custom-settings/_index.md index a232ee7754a..41e98236118 100644 --- a/content/en/docs/refguide10/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide10/runtime/custom-settings/_index.md @@ -121,8 +121,8 @@ The settings below influence the behavior of the log files. These settings can o | DatabaseType | Defines the database engine which is used as the Mendix database. Valid values are `HSQLDB`, `MYSQL`, `ORACLE`, `POSTGRESQL`, `SAPHANA`, and `SQLSERVER`. | | | DatabaseUserName | Name required for authentication to the database. | | | DatabasePassword | Password for the `DatabaseUserName` supplied above. | | -| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). | | -| DatabaseName | The name of the database or schema used by the Mendix app
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). | | +| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). +| DatabaseName | The name of the database or schema used by the Mendix app
Depending on the database type, it is required even if a `DatabaseJdbcUrl` is defined. | | | DatabaseJdbcUrl | Defines the JDBC URL to use for the database connection (which overrides the other database connection settings). | | | DatabaseUseSsl | When `true`, the connection will be made using SSL without certificate validation. If you need certificate validation, use [DatabaseJdbcUrl](#DatabaseJdbcUrl) instead.
When `false`, the connection will be made without SSL (this is only relevant for SQL Server, which uses SSL by default). | | | DatabaseUseIntegratedSecurity | This setting defines whether integrated security will be used to authenticate to SQL Server. If true, user name and password will not be used.
Ensure that the proper domain user for accessing the SQL Server is authenticated on the runtime server using the `kinit` command. | false | diff --git a/content/en/docs/refguide9/runtime/custom-settings/_index.md b/content/en/docs/refguide9/runtime/custom-settings/_index.md index e9c9ca3d1b8..64d54c13bb5 100644 --- a/content/en/docs/refguide9/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide9/runtime/custom-settings/_index.md @@ -97,8 +97,8 @@ The settings below influence the behavior of the log files. These settings can o | DatabaseType | Defines the database engine which is used as the Mendix database. Valid values are `DB2`, `HSQLDB`, `MYSQL`, `ORACLE`, `POSTGRESQL`, `SAPHANA`, and `SQLSERVER`. | | | DatabaseUserName | Name required for authentication to the database. | | | DatabasePassword | Password for the `DatabaseUserName` supplied above. | | -| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply `DatabaseJdbcUrl`. | | -| DatabaseName | The name of the database or schema used by the Mendix app
This will be overridden if you supply **DatabaseJdbcUrl**. | | +| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). +| DatabaseName | The name of the database or schema used by the Mendix app
Depending on the database type, it is required even if a `DatabaseJdbcUrl` is defined. | | | DatabaseJdbcUrl | Defines the JDBC URL to use for the database connection (which overrides the other database connection settings). | | | DatabaseUseSsl | For PostgreSQL databases, defines whether the connection will be made using SSL without certificate validation. If you need certificate validation, use **DatabaseJdbcUrl** instead. | false | | DatabaseUseIntegratedSecurity | This setting defines whether integrated security will be used to authenticate to SQL Server. If true, user name and password will not be used.
If the runtime is not running on Windows, it must be instructed to use JavaKerberos authentication: for versions of Mendix below 9.23.0, add `;integratedSecurity=true;authenticationScheme=JavaKerberos` to **DatabaseJdbcUrl**. In addition, ensure that the proper domain user for accessing the SQL Server is authenticated on the runtime server using the `kinit` command. | false | From c403c4c5cb150151a92c33d3844b5ecefa8857a1 Mon Sep 17 00:00:00 2001 From: Augusto Passalacqua Date: Tue, 30 Sep 2025 17:28:24 +0200 Subject: [PATCH 3/7] Update DatabaseName description for Mendix 11 Co-authored-by: Mark van Ments <35492184+MarkvanMents@users.noreply.github.com> --- content/en/docs/refguide/runtime/custom-settings/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/refguide/runtime/custom-settings/_index.md b/content/en/docs/refguide/runtime/custom-settings/_index.md index 3aa6f53f200..5591bcfe74d 100644 --- a/content/en/docs/refguide/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide/runtime/custom-settings/_index.md @@ -125,7 +125,7 @@ The settings below influence the behavior of the log files. These settings can o | DatabaseUserName | Name required for authentication to the database. | | | DatabasePassword | Password for the `DatabaseUserName` supplied above. | | | DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). -| DatabaseName | The name of the database or schema used by the Mendix app
Depending on the database type, it is required even if a `DatabaseJdbcUrl` is defined. | | +| DatabaseName | The name of the database or schema used by the Mendix app
Some database types require this even if a `DatabaseJdbcUrl` is defined. | | | DatabaseJdbcUrl | Defines the JDBC URL to use for the database connection (which overrides the other database connection settings). | | | DatabaseUseSsl | When `true`, the connection will be made using SSL without certificate validation. If you need certificate validation, use [DatabaseJdbcUrl](#DatabaseJdbcUrl) instead.
When `false`, the connection will be made without SSL (this is only relevant for SQL Server, which uses SSL by default). | | | DatabaseUseIntegratedSecurity | This setting defines whether integrated security will be used to authenticate to SQL Server. If true, user name and password will not be used.
Ensure that the proper domain user for accessing the SQL Server is authenticated on the runtime server using the `kinit` command. | false | From 806140db1a5dd4bae7975c44fb0da5642a1c5b9e Mon Sep 17 00:00:00 2001 From: Augusto Passalacqua Date: Tue, 30 Sep 2025 17:29:40 +0200 Subject: [PATCH 4/7] Update DatabaseName description for Mendix 10 and 9 --- content/en/docs/refguide10/runtime/custom-settings/_index.md | 2 +- content/en/docs/refguide9/runtime/custom-settings/_index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/refguide10/runtime/custom-settings/_index.md b/content/en/docs/refguide10/runtime/custom-settings/_index.md index 41e98236118..75f120b0ea0 100644 --- a/content/en/docs/refguide10/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide10/runtime/custom-settings/_index.md @@ -122,7 +122,7 @@ The settings below influence the behavior of the log files. These settings can o | DatabaseUserName | Name required for authentication to the database. | | | DatabasePassword | Password for the `DatabaseUserName` supplied above. | | | DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). -| DatabaseName | The name of the database or schema used by the Mendix app
Depending on the database type, it is required even if a `DatabaseJdbcUrl` is defined. | | +| DatabaseName | The name of the database or schema used by the Mendix app
Some database types require this even if a `DatabaseJdbcUrl` is defined. | | | DatabaseJdbcUrl | Defines the JDBC URL to use for the database connection (which overrides the other database connection settings). | | | DatabaseUseSsl | When `true`, the connection will be made using SSL without certificate validation. If you need certificate validation, use [DatabaseJdbcUrl](#DatabaseJdbcUrl) instead.
When `false`, the connection will be made without SSL (this is only relevant for SQL Server, which uses SSL by default). | | | DatabaseUseIntegratedSecurity | This setting defines whether integrated security will be used to authenticate to SQL Server. If true, user name and password will not be used.
Ensure that the proper domain user for accessing the SQL Server is authenticated on the runtime server using the `kinit` command. | false | diff --git a/content/en/docs/refguide9/runtime/custom-settings/_index.md b/content/en/docs/refguide9/runtime/custom-settings/_index.md index 64d54c13bb5..a5478d8b9b5 100644 --- a/content/en/docs/refguide9/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide9/runtime/custom-settings/_index.md @@ -98,7 +98,7 @@ The settings below influence the behavior of the log files. These settings can o | DatabaseUserName | Name required for authentication to the database. | | | DatabasePassword | Password for the `DatabaseUserName` supplied above. | | | DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). -| DatabaseName | The name of the database or schema used by the Mendix app
Depending on the database type, it is required even if a `DatabaseJdbcUrl` is defined. | | +| DatabaseName | The name of the database or schema used by the Mendix app
Some database types require this even if a `DatabaseJdbcUrl` is defined. | | | DatabaseJdbcUrl | Defines the JDBC URL to use for the database connection (which overrides the other database connection settings). | | | DatabaseUseSsl | For PostgreSQL databases, defines whether the connection will be made using SSL without certificate validation. If you need certificate validation, use **DatabaseJdbcUrl** instead. | false | | DatabaseUseIntegratedSecurity | This setting defines whether integrated security will be used to authenticate to SQL Server. If true, user name and password will not be used.
If the runtime is not running on Windows, it must be instructed to use JavaKerberos authentication: for versions of Mendix below 9.23.0, add `;integratedSecurity=true;authenticationScheme=JavaKerberos` to **DatabaseJdbcUrl**. In addition, ensure that the proper domain user for accessing the SQL Server is authenticated on the runtime server using the `kinit` command. | false | From e7693b0783ee384e40b5e9774defd631855891d7 Mon Sep 17 00:00:00 2001 From: Augusto Passalacqua Date: Wed, 1 Oct 2025 10:00:29 +0200 Subject: [PATCH 5/7] Change info note about DataStorage_QueryPlan from trace to debug and reword messages --- .../domain-model/entities/view-entities/use-view-entities.md | 4 ++-- .../domain-model/entities/view-entities/use-view-entities.md | 2 +- content/en/docs/refguide10/runtime/logging/_index.md | 2 +- content/en/docs/refguide8/runtime/logging.md | 2 +- content/en/docs/refguide9/runtime/logging.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md index 524c3184e1a..5fd6340a46c 100644 --- a/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md +++ b/content/en/docs/refguide/modeling/domain-model/entities/view-entities/use-view-entities.md @@ -173,10 +173,10 @@ The database follows the below process: Even though the query is using a view that also includes address information, the database ignores this information, as it is not relevant when counting customers by age. -If you set the `DataStorage_QueryPlan` log node to Trace, you see the query plan for your all your queries in the Mendix Runtime log. +If you set the `DataStorage_QueryPlan` log node to Debug, you see the query plan for all your queries in the Mendix Runtime log. {{% alert color="warning" %}} -The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production. +The `DataStorage_QueryPlan` log node has a very large performance impact and should never be enabled in production. {{% /alert %}} ## Read More diff --git a/content/en/docs/refguide10/modeling/domain-model/entities/view-entities/use-view-entities.md b/content/en/docs/refguide10/modeling/domain-model/entities/view-entities/use-view-entities.md index b9d8ddb27a1..6dfcbd50542 100644 --- a/content/en/docs/refguide10/modeling/domain-model/entities/view-entities/use-view-entities.md +++ b/content/en/docs/refguide10/modeling/domain-model/entities/view-entities/use-view-entities.md @@ -127,7 +127,7 @@ Even though the query is using a view that also includes address information, th If you set the `DataStorage_QueryPlan` log node to Trace, you see the query plan for all your queries in the Mendix Runtime log. {{% alert color="warning" %}} -The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production. +The `DataStorage_QueryPlan` log node has a very large performance impact and should never be enabled in production. {{% /alert %}} ## Read More diff --git a/content/en/docs/refguide10/runtime/logging/_index.md b/content/en/docs/refguide10/runtime/logging/_index.md index 476719454b0..056c69245b9 100644 --- a/content/en/docs/refguide10/runtime/logging/_index.md +++ b/content/en/docs/refguide10/runtime/logging/_index.md @@ -64,7 +64,7 @@ This list is currently incomplete and is being updated. | Connector | Logs when standard or custom request handlers (added through Core#addRequestHandler) are registered, or when a path is called that does not have a registered request handler. | | Core | Logs messages from the core runtime. This can be startup of the runtime, version of the runtime, license being used and issues related to interpreting the model. | | DataStorage_QueryHandling | Logs messages related to the queries that are being executed. | -| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production.{{% /alert %}} | +| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should never be enabled in production.{{% /alert %}} | | DocumentExporter | Logs messages related to the templating engine that generates documents. | | FileDocumentSizesPopulateJob | Logs messages for a background job that populates the file-size field in the database for documents that do not have that field filled (used during legacy migration). | | InvalidRequestLimiter | Logs messages related to responses being throttled due to invalid requests. | diff --git a/content/en/docs/refguide8/runtime/logging.md b/content/en/docs/refguide8/runtime/logging.md index 4f48dbe7231..d182266d2ee 100644 --- a/content/en/docs/refguide8/runtime/logging.md +++ b/content/en/docs/refguide8/runtime/logging.md @@ -61,7 +61,7 @@ This list is currently incomplete and is being worked on. | Connector | | | Core | Logs messages from the core runtime. This can be startup of the runtime, version of the runtime, license being used and issues related to interpreting the model. | | DataStorage_QueryHandling | Logs messages related to the queries that are being executed. | -| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production.{{% /alert %}} +| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should never be enabled in production.{{% /alert %}} | | DocumentExporter | Logs messages related to the templating engine that generates documents. | | FileDocumentSizesPopulateJob | Logs messages for a background job that populates the file-size field in the database for documents that do not have that field filled (used during legacy migration). | | I18NProcessor | Logs messages related to translation of the app. | diff --git a/content/en/docs/refguide9/runtime/logging.md b/content/en/docs/refguide9/runtime/logging.md index 92b23eafc4e..ff4bfc0b64b 100644 --- a/content/en/docs/refguide9/runtime/logging.md +++ b/content/en/docs/refguide9/runtime/logging.md @@ -64,7 +64,7 @@ This list is currently incomplete and is being updated. | Connector | | | Core | Logs messages from the core runtime. This can be startup of the runtime, version of the runtime, license being used and issues related to interpreting the model. | | DataStorage_QueryHandling | Logs messages related to the queries that are being executed. | -| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should not be enabled in production.{{% /alert %}} +| DataStorage_QueryPlan | Logs the query plan used by the database for every query (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should never be enabled in production.{{% /alert %}} | | DocumentExporter | Logs messages related to the templating engine that generates documents. | | FileDocumentSizesPopulateJob | Logs messages for a background job that populates the file-size field in the database for documents that do not have that field filled (used during legacy migration). | | IDResolution | Information on retrieval queries and runtime operations that are being executed. | From b28f6f076d024c2e107b2b027e04494bd1814751 Mon Sep 17 00:00:00 2001 From: Augusto Passalacqua Date: Wed, 1 Oct 2025 10:05:40 +0200 Subject: [PATCH 6/7] Add QueryPlan warning in logging page for mx 11 as well --- content/en/docs/refguide/runtime/logging/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/refguide/runtime/logging/_index.md b/content/en/docs/refguide/runtime/logging/_index.md index 7a5d62a2ef4..cdd450428f2 100644 --- a/content/en/docs/refguide/runtime/logging/_index.md +++ b/content/en/docs/refguide/runtime/logging/_index.md @@ -68,7 +68,7 @@ This list is currently incomplete and is being updated. | Connector | Logs when standard or custom request handlers (added through Core#addRequestHandler) are registered, or when a path is called that does not have a registered request handler. | | Core | Logs messages from the core runtime. This can be startup of the runtime, version of the runtime, license being used and issues related to interpreting the model. | | DataStorage_QueryHandling | Logs messages related to the queries that are being executed. | -| DataStorage_QueryPlan | Query execution plan information for installations (currently only supported for PostgreSQL databases). | +| DataStorage_QueryPlan | Query execution plan information for installations (currently only supported for PostgreSQL databases). {{% alert color="warning" %}}The `DataStorage_QueryPlan` log node has a very large performance impact and should never be enabled in production.{{% /alert %}} | | DocumentExporter | Logs messages related to the templating engine that generates documents. | | FileDocumentSizesPopulateJob | Logs messages for a background job that populates the file-size field in the database for documents that do not have that field filled (used during legacy migration). | | InvalidRequestLimiter | Logs messages related to responses being throttled due to invalid requests. | From 1414bb7bff762bdefbba681753ea46a6569f9544 Mon Sep 17 00:00:00 2001 From: MarkvanMents Date: Wed, 1 Oct 2025 17:08:17 +0200 Subject: [PATCH 7/7] Fix broken tables --- content/en/docs/refguide/runtime/custom-settings/_index.md | 2 +- content/en/docs/refguide10/runtime/custom-settings/_index.md | 2 +- content/en/docs/refguide9/runtime/custom-settings/_index.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/refguide/runtime/custom-settings/_index.md b/content/en/docs/refguide/runtime/custom-settings/_index.md index 5591bcfe74d..4e14f24cf37 100644 --- a/content/en/docs/refguide/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide/runtime/custom-settings/_index.md @@ -124,7 +124,7 @@ The settings below influence the behavior of the log files. These settings can o | DatabaseType | Defines the database engine which is used as the Mendix database. Valid values are `HSQLDB`, `MYSQL`, `ORACLE`, `POSTGRESQL`, `SAPHANA`, and `SQLSERVER`. | | | DatabaseUserName | Name required for authentication to the database. | | | DatabasePassword | Password for the `DatabaseUserName` supplied above. | | -| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). +| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). | | | DatabaseName | The name of the database or schema used by the Mendix app
Some database types require this even if a `DatabaseJdbcUrl` is defined. | | | DatabaseJdbcUrl | Defines the JDBC URL to use for the database connection (which overrides the other database connection settings). | | | DatabaseUseSsl | When `true`, the connection will be made using SSL without certificate validation. If you need certificate validation, use [DatabaseJdbcUrl](#DatabaseJdbcUrl) instead.
When `false`, the connection will be made without SSL (this is only relevant for SQL Server, which uses SSL by default). | | diff --git a/content/en/docs/refguide10/runtime/custom-settings/_index.md b/content/en/docs/refguide10/runtime/custom-settings/_index.md index 75f120b0ea0..9d37b55cd99 100644 --- a/content/en/docs/refguide10/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide10/runtime/custom-settings/_index.md @@ -121,7 +121,7 @@ The settings below influence the behavior of the log files. These settings can o | DatabaseType | Defines the database engine which is used as the Mendix database. Valid values are `HSQLDB`, `MYSQL`, `ORACLE`, `POSTGRESQL`, `SAPHANA`, and `SQLSERVER`. | | | DatabaseUserName | Name required for authentication to the database. | | | DatabasePassword | Password for the `DatabaseUserName` supplied above. | | -| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). +| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). | | | DatabaseName | The name of the database or schema used by the Mendix app
Some database types require this even if a `DatabaseJdbcUrl` is defined. | | | DatabaseJdbcUrl | Defines the JDBC URL to use for the database connection (which overrides the other database connection settings). | | | DatabaseUseSsl | When `true`, the connection will be made using SSL without certificate validation. If you need certificate validation, use [DatabaseJdbcUrl](#DatabaseJdbcUrl) instead.
When `false`, the connection will be made without SSL (this is only relevant for SQL Server, which uses SSL by default). | | diff --git a/content/en/docs/refguide9/runtime/custom-settings/_index.md b/content/en/docs/refguide9/runtime/custom-settings/_index.md index a5478d8b9b5..d4514eb5e56 100644 --- a/content/en/docs/refguide9/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide9/runtime/custom-settings/_index.md @@ -97,7 +97,7 @@ The settings below influence the behavior of the log files. These settings can o | DatabaseType | Defines the database engine which is used as the Mendix database. Valid values are `DB2`, `HSQLDB`, `MYSQL`, `ORACLE`, `POSTGRESQL`, `SAPHANA`, and `SQLSERVER`. | | | DatabaseUserName | Name required for authentication to the database. | | | DatabasePassword | Password for the `DatabaseUserName` supplied above. | | -| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). +| DatabaseHost | The host name and optionally the TCP port number of the database. Use a colon (`:`) as separator between the host name and port number. Possible values are: `db.url.org`, `db.url.org:1521`, `10.0.0.5`, and`10.0.0.5:1433`\. It is possible to use a plain IPv6 address by enclosing it in brackets (for example, `[::1]:5432`).
This will be overridden if you supply [DatabaseJdbcUrl](#DatabaseJdbcUrl). | | | DatabaseName | The name of the database or schema used by the Mendix app
Some database types require this even if a `DatabaseJdbcUrl` is defined. | | | DatabaseJdbcUrl | Defines the JDBC URL to use for the database connection (which overrides the other database connection settings). | | | DatabaseUseSsl | For PostgreSQL databases, defines whether the connection will be made using SSL without certificate validation. If you need certificate validation, use **DatabaseJdbcUrl** instead. | false |