From 8f4f2a10651fc6dfc57b9f7cec64c4df1e643711 Mon Sep 17 00:00:00 2001 From: mahendra-mahajan-mendix <90612240+mahendra-mahajan-mendix@users.noreply.github.com> Date: Mon, 6 Jan 2025 18:14:16 +0530 Subject: [PATCH 1/2] Update connector-guide-best-practices.md add a caveat for unlimited string for sorting or grouping by operations. --- .../create-connectors/connector-guide-best-practices.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/content/en/docs/appstore/create-content/create-connectors/connector-guide-best-practices.md b/content/en/docs/appstore/create-content/create-connectors/connector-guide-best-practices.md index 0ef94c5315b..f4ace6686dc 100644 --- a/content/en/docs/appstore/create-content/create-connectors/connector-guide-best-practices.md +++ b/content/en/docs/appstore/create-content/create-connectors/connector-guide-best-practices.md @@ -192,6 +192,9 @@ Toolbox actions need clear naming, consistent categorization, and documentation, Consider doing the following for all entity attributes: * Set all string values to unlimited. +{{% alert color="info" %}} +Attributes that are used for sorting or group by operations should not be set to unlimited as databases like SAP HANA, Oracle do NOT support CLOBs for order by or group by clauses. +{{% /alert %}} * Check all date values. If the service only returns a date (no time), then set **localize** to *No*. * Check all number values (decimal, integer, long), and remove the default value of 0. From 5f7d0368e18eb966c431d93187c97a07339c9cf8 Mon Sep 17 00:00:00 2001 From: quinntracy Date: Mon, 6 Jan 2025 14:31:19 +0100 Subject: [PATCH 2/2] Revise --- .../create-connectors/connector-guide-best-practices.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/content/en/docs/appstore/create-content/create-connectors/connector-guide-best-practices.md b/content/en/docs/appstore/create-content/create-connectors/connector-guide-best-practices.md index f4ace6686dc..e7ea41dbfdf 100644 --- a/content/en/docs/appstore/create-content/create-connectors/connector-guide-best-practices.md +++ b/content/en/docs/appstore/create-content/create-connectors/connector-guide-best-practices.md @@ -192,12 +192,14 @@ Toolbox actions need clear naming, consistent categorization, and documentation, Consider doing the following for all entity attributes: * Set all string values to unlimited. -{{% alert color="info" %}} -Attributes that are used for sorting or group by operations should not be set to unlimited as databases like SAP HANA, Oracle do NOT support CLOBs for order by or group by clauses. -{{% /alert %}} * Check all date values. If the service only returns a date (no time), then set **localize** to *No*. * Check all number values (decimal, integer, long), and remove the default value of 0. +{{% alert color="info" %}} + +Databases like SAP HANA and Oracle do not support CLOBs for order by or group by clauses. Because of this, attributes that are used for sorting or group by operations should not be set to unlimited. +{{% /alert %}} + ### Dependencies Given that there is no dependency management between Mendix modules, try to minimize the number of dependencies your module has on other modules. If you do have to depend on other modules, make sure those modules are well-maintained by you or by Mendix themselves. Introducing another community-supported module as a dependent module might be too much of a risk for developers wanting to use your module.