From 660a8d53fbe83669c251f684e8a41c7f356ff2b6 Mon Sep 17 00:00:00 2001
From: hjboth <124381150+hjboth@users.noreply.github.com>
Date: Mon, 17 Jun 2024 16:55:45 +0200
Subject: [PATCH 1/2] hard coded vs usr defined strlength

... make foot note clearer
---
 cds/types.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cds/types.md b/cds/types.md
index 1c8441294..a3a18f2ec 100644
--- a/cds/types.md
+++ b/cds/types.md
@@ -47,7 +47,7 @@ The following built-in types are provided:
 
 > <sup>(4)</sup> Up to 7 digits of fractional seconds; if a data is given with higher precision truncation may occur
 
-> <sup>(5)</sup> Argument `length` is optional → use options `cds.cdsc.defaultStringLength` and `cds.cdsc.defaultBinaryLength` to control the project-specific default length used for OData and SQL backends. The default length is 5000 for SAP HANA and 255 for all other SQL backends. Note that default lengths are only applied on database level. Specify fixed lengths to get length checks on service level and/or inbound data.
+> <sup>(5)</sup> Argument `length` is optional → use options `cds.cdsc.defaultStringLength` and `cds.cdsc.defaultBinaryLength` to control the project-specific default length used for OData and SQL backends. If no option is specified, a hard-coded default length of 5000 for SAP HANA and 255 for all other SQL backends applies. Note that this hard-coded default lengths are only applied on database level. Specify fixed lengths to get length checks on service level and/or inbound data.
 
 > <sup>(6)</sup> Mapping to ANSI SQL types are given for comparison. Note though, that you need to have the specification of your target database in mind when considering, for example, length restrictions.
 

From 7b38ee92ba43f5ff442f85c3d6028c57dc6e46e5 Mon Sep 17 00:00:00 2001
From: Steffen Weinstock <79531202+stewsk@users.noreply.github.com>
Date: Tue, 18 Jun 2024 10:09:50 +0200
Subject: [PATCH 2/2] Update cds/types.md

Co-authored-by: Andre Meyering <andre.meyering@sap.com>
---
 cds/types.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cds/types.md b/cds/types.md
index a3a18f2ec..6f82d8719 100644
--- a/cds/types.md
+++ b/cds/types.md
@@ -47,7 +47,7 @@ The following built-in types are provided:
 
 > <sup>(4)</sup> Up to 7 digits of fractional seconds; if a data is given with higher precision truncation may occur
 
-> <sup>(5)</sup> Argument `length` is optional → use options `cds.cdsc.defaultStringLength` and `cds.cdsc.defaultBinaryLength` to control the project-specific default length used for OData and SQL backends. If no option is specified, a hard-coded default length of 5000 for SAP HANA and 255 for all other SQL backends applies. Note that this hard-coded default lengths are only applied on database level. Specify fixed lengths to get length checks on service level and/or inbound data.
+> <sup>(5)</sup> Argument `length` is optional → use options `cds.cdsc.defaultStringLength` and `cds.cdsc.defaultBinaryLength` to control the project-specific default length used for OData and SQL backends. If no option is specified, a hard-coded default length of 5000 for SAP HANA and 255 for all other SQL backends applies. Note that these hard-coded default lengths are only applied on database level. Specify fixed lengths to get length checks on service level and/or inbound data.
 
 > <sup>(6)</sup> Mapping to ANSI SQL types are given for comparison. Note though, that you need to have the specification of your target database in mind when considering, for example, length restrictions.