hard coded vs usr defined strlength (#1017)

* hard coded vs usr defined strlength

... make foot note clearer

* Update cds/types.md

Co-authored-by: Andre Meyering <andre.meyering@sap.com>

---------

Co-authored-by: Steffen Weinstock <79531202+stewsk@users.noreply.github.com>
Co-authored-by: Andre Meyering <andre.meyering@sap.com>

Author: 3 people

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 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.