From 89c81999358066e1dc407bf0e53719583c264e6e Mon Sep 17 00:00:00 2001 From: Bas de Bakker Date: Fri, 28 Mar 2025 13:28:44 +0100 Subject: [PATCH] Update default value of OptimizeSecurityColumns --- 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 71284434e45..f1d6d778b2f 100644 --- a/content/en/docs/refguide/runtime/custom-settings/_index.md +++ b/content/en/docs/refguide/runtime/custom-settings/_index.md @@ -132,7 +132,7 @@ The settings below influence the behavior of the log files. These settings can o | UseNetworkTimeout | This setting is applied to PostgreSQL. It affects the timeout mechanism used when reserving new ids for Mendix objects. If set to true, the socket level request timeout is used. In that case, the request timeout is handled within the operating system. If set to false, the timeout is handled by Mendix runtime. For other databases, timeouts are always handled by Mendix runtime. | true | | JdbcLoginTimeout | This setting defines the database connection establishment time in milliseconds. | 5000 (5 seconds) | | com.mendix.offline.SynchronizationCleanupInterval | This setting defines how often objects of type `System.OfflineSynchronizationHistory` are cleaned up. | 90 (90 days) | -| DataStorage.OptimizeSecurityColumns | When true, query columns generated to evaluate XPath constraints in access rules are optimized to `true` if the runtime can determine that the value will always be true for the objects that the query returns. This is almost always an improvement, but we have seen cases where the PostgreSQL query planner has worse performance for the simpler query. Supported since Mendix 10.17 | false | +| DataStorage.OptimizeSecurityColumns | When true, query columns generated to evaluate XPath constraints in access rules are optimized to `true` if the runtime can determine that the value will always be true for the objects that the query returns. This is almost always an improvement, but we have seen cases where the PostgreSQL query planner has worse performance for the simpler query. | true | ### Connection Pooling {#connection-pooling}