Merge branch 'main' into cxl

Author: Akatuoro

cds/types.md

@@ -10,55 +10,40 @@ status: released
 # Core / Built-in Types
 
 
-The following table lists the built-in types available to all CDS models, and can be used to define entity elements or custom types as follows:
-
-```cds
-entity Books {
-  key ID : UUID;
-  title  : String(111);
-  stock  : Integer;
-  price  : Price;
-}
-type Price : Decimal;
-```
-
-These types are used to define the structure of entities and services, and are mapped to respective database types when the model is deployed.
-
-| CDS Type | Remarks | ANSI SQL <sup>(1)</sup> |
-| --- | --- | --- |
-| `UUID` | CAP generates [RFC 4122](https://tools.ietf.org/html/rfc4122)-compliant UUIDs <sup>(2)</sup> | _NVARCHAR(36)_  |
-| `Boolean` | Values: `true`, `false`, `null`, `0`, `1` | _BOOLEAN_  |
-| `Integer` | Same as `Int32` by default | _INTEGER_  |
-| `Int16` | Signed 16-bit integer, range *[ -2<sup>15</sup> ... +2<sup>15</sup> )* | _SMALLINT_  |
-| `Int32` | Signed 32-bit integer, range *[ -2<sup>31</sup> ... +2<sup>31</sup> )* | _INTEGER_  |
-| `Int64` | Signed 64-bit integer, range *[ -2<sup>63</sup> ... +2<sup>63</sup> )* | _BIGINT_  |
-| `UInt8` | Unsigned 8-bit integer, range *[ 0 ... 255 ]* | _TINYINT_ <sup>(3)</sup> |
-| `Decimal` (`prec`, `scale`) | A *decfloat* type is used if arguments are omitted | _DECIMAL_  |
-| `Double` | Floating point with binary mantissa | _DOUBLE_  |
-| `Date` | e.g. `2022-12-31` | _DATE_  |
-| `Time` | e.g. `23:59:59` | _TIME_  |
-| `DateTime` | _sec_ precision | _TIMESTAMP_  |
-| `Timestamp` | _µs_ precision, with up to 7 fractional digits |  _TIMESTAMP_  |
-| `String` (`length`) | Default *length*: 255; on HANA: 5000 <sup>(4)(5)</sup> | _NVARCHAR_  |
-| `Binary` (`length`) | Default *length*: 255; on HANA: 5000 <sup>(4)(6)</sup> |  _VARBINARY_  |
-| `LargeBinary` | Unlimited data, usually streamed at runtime<br/>[Prefer using Attachments plugin for large files](../plugins/index.md#attachments) | _BLOB_ |
-| `LargeString` | Unlimited data, usually streamed at runtime | _NCLOB_  |
-| `Map` | Mapped to *NCLOB* for HANA. | *JSON* type |
-| `Vector` (`dimension `) | Requires SAP HANA Cloud QRC 1/2024, or later |  _REAL_VECTOR_  |
-
-> <sup>(1)</sup> Concrete mappings to specific databases may differ.
->
-> <sup>(2)</sup> See also [Best Practices](../guides/domain/index#don-t-interpret-uuids).
->
-> <sup>(3)</sup> _SMALLINT_ on PostgreSQL and H2.
->
-> <sup>(4)</sup> Productive apps should always use an explicit length. Use the default only for rapid prototyping.
->
-> <sup>(5)</sup> Configurable through `cds.cdsc.defaultStringLength`.
->
-> <sup>(6)</sup> Configurable through `cds.cdsc.defaultBinaryLength`.
-
-#### See also...
+The following table lists the built-in types in CDS, and their most common mapping to
+ANSI SQL types, when deployed to a relational database (concrete mappings to specific databases may differ):
+
+| CDS Type            | Remarks                                                                | ANSI SQL       |
+|---------------------|------------------------------------------------------------------------|----------------|
+| `UUID`              | [RFC 4122](https://tools.ietf.org/html/rfc4122)-compliant UUIDs        | _NVARCHAR(36)_ |
+| `Boolean`           | Values: `true`, `false`, `null`, `0`, `1`                              | _BOOLEAN_      |
+| `Integer`           | Same as `Int32` by default                                             | _INTEGER_      |
+| `Int16`             | Signed 16-bit integer, range *[ -2<sup>15</sup> ... +2<sup>15</sup> )* | _SMALLINT_     |
+| `Int32`             | Signed 32-bit integer, range *[ -2<sup>31</sup> ... +2<sup>31</sup> )* | _INTEGER_      |
+| `Int64`             | Signed 64-bit integer, range *[ -2<sup>63</sup> ... +2<sup>63</sup> )* | _BIGINT_       |
+| `UInt8`             | Unsigned 8-bit integer, range *[ 0 ... 255 ]*                          | _TINYINT_      |
+| `Decimal`(`p`,`s`)  | Decimal with precision `p` and scale `s`                               | _DECIMAL_      |
+| `Double`            | Floating point with binary mantissa                                    | _DOUBLE_       |
+| `Date`              | e.g. `2022-12-31`                                                      | _DATE_         |
+| `Time`              | e.g. `23:59:59`                                                        | _TIME_         |
+| `DateTime`          | _sec_ precision                                                        | _TIMESTAMP_    |
+| `Timestamp`         | _µs_ precision, with up to 7 fractional digits                         | _TIMESTAMP_    |
+| `String` (`length`) | Default *length*: 255; on HANA: 5000                                   | _NVARCHAR_     |
+| `Binary` (`length`) | Default *length*: 255; on HANA: 5000                                   | _VARBINARY_    |
+| `Vector` (`length`) | SAP HANA Cloud QRC 1/2024, or later only                               | _REAL_VECTOR_  |
+| `LargeBinary`       | Unlimited binary data, usually streamed at runtime                     | _BLOB_         |
+| `LargeString`       | Unlimited textual data, usually streamed at runtime                    | _NCLOB_        |
+| `Map`               | Mapped to *NCLOB* for HANA.                                            | *JSON* type    |
+
+> [!info] Default String Lengths
+> Lengths can be omitted, in which case default lengths are used. While this is usual in initial phases of a project, productive apps should always use explicitly defined length. The respective default lengths are configurable through the config options
+> <Config> cds.cdsc.defaultStringLength = 255 </Config> and <br/>
+> <Config> cds.cdsc.defaultBinaryLength = 255 </Config>.
+
+> [!tip] Use Attachments instead of LargeBinary
+> Consider using _Attachments_, as provided through [the CAP Attachments plugins](../plugins/index#attachments), instead of `LargeBinary` types for user-generated content like documents, images, etc.
+
+See also:
 
 [Additional Reuse Types and Aspects by `@sap/cds/common`](common) {.learn-more}
 

get-started/feature-matrix.md

@@ -114,8 +114,7 @@ Following is an index of the features currently covered by CAP, with status and
 | [Arrayed Elements](../cds/cdl#arrayed-types)                                                        | <X/>  |  <X/>   | <X/> |
 | [Streaming & Media Types](../guides/services/media-data)                 | <X/>  |  <X/>   | <X/> |
 | [Conflict Detection through _ETags_](../guides/services/served-ootb#etag)                    | <X/>  |  <X/>   | <X/> |
-| [Authentication via JWT](../guides/security/authorization#prerequisite-authentication)              | <Na/> |  <X/>   | <X/> |
-| [Mocked Authentication](../guides/security/authorization#prerequisite-authentication)               | <Na/> |  <X/>   | <X/> |
+| [Authentication](../guides/security/authentication)                                        | <X/> |  <X/>   | <X/> |
 
 
 <br>

get-started/get-help.md

@@ -292,7 +292,7 @@ A new option `privilegedUser()` can be leveraged when [defining](../java/event-h
 
 |              | Explanation                                                                                                                                                                                            |
 |--------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| _Root Cause_ | You've [explicitly configured a mock](../java/security#explicitly-defined-mock-users) user with a name that is already used by a [preconfigured mock user](../java/security#preconfigured-mock-users). |
+| _Root Cause_ | You've [explicitly configured a mock](../java/security#custom-mock-users) user with a name that is already used by a [preconfigured mock user](../java/security#preconfigured-mock-users). |
 | _Solution_   | Rename the mock user and build your project again.                                                                                                                                                     |
 
 ### Why do I get an "Error on server start"?
@@ -678,7 +678,7 @@ By default, the Cloud MTA Build Tool executes module builds in parallel. If you
 
 `cf undeploy <mta-id>` deletes an MTA (use `cf mtas` to find the MTA ID).
 
-Use the optional `--delete-services` parameter to also wipe service instances.
+Use `--delete-services`, `--delete-service-keys` and `--delete-service-brokers` parameters to also wipe services, service keys, or service brokers.
 
 ::: danger This also deletes the HDI containers with the application data.
 :::

get-started/index.md

@@ -49,8 +49,8 @@ Then install CAP's _cds-dk_ globally:
 ### Node.js and _cds-dk_ {.required}
 
 ```shell
-brew install node@24             # Node.js latest LTS
-npm add --global @sap/cds-dk     # CAP's cds-dk
+brew install node      # Node.js latest LTS
+npm i -g @sap/cds-dk   # CAP's cds-dk
 ```
 
 
@@ -60,10 +60,6 @@ npm add --global @sap/cds-dk     # CAP's cds-dk
 brew install sapmachine-jdk
 brew install maven
 ```
-```shell
-code --install-extension oracle.oracle-java       # for Java
-code --install-extension vscjava.vscode-maven     # for Maven
-```
 
 
 ### Git and GitHub {.optional}
@@ -80,12 +76,18 @@ brew install github    # GitHub Desktop App
 
 ```shell
 brew install --cask visual-studio-code            # VS Code itself
+```
+```shell
 code --install-extension sapse.vscode-cds         # for .cds models
 code --install-extension mechatroner.rainbow-csv  # for .csv files
 code --install-extension qwtel.sqlite-viewer      # for .sqlite files
 code --install-extension humao.rest-client        # for REST requests
 code --install-extension dbaeumer.vscode-eslint   # for linting
 ```
+```shell
+code --install-extension oracle.oracle-java       # for Java
+code --install-extension vscjava.vscode-maven     # for Maven
+```
 
 
 > You can of course also use other IDEs or editors of your choice, such as [IntelliJ IDEA](https://www.jetbrains.com/idea/), for which we also provide [support](../tools/cds-editors#intellij). Yet we strongly recommend Visual Studio Code for the best experience with CAP.

guides/databases/cdl-to-ddl.md

@@ -345,9 +345,9 @@ LEFT JOIN Genres as genre on genre_ID = genre.ID; -- [!code ++]
 ```
 :::
 
-> [!tip] Associations as <i>Forward-declared JOINs</i>
+> [!tip] Associations as <i>'Forward-declared' JOINs</i>
 > Looking closely at the above compiled SQL code, we can regard 
-> associations to be like _'Forward-declared JOINs'_, along these lines: 
+> associations to be like _'Forward-declared' JOINs_, along these lines: 
 >
 > 1. Association names `a.name` appear in queries as standard _table aliases_ 
 > 2. _JOINs_ are added automatically as per the following construction rule: 

guides/deploy/microservices.md

@@ -370,7 +370,7 @@ Note that we use the *--ws-pack* option for some modules. It's important for nod
 
 ### Authentication
 
-Add [security configuration](../security/authorization#xsuaa-configuration) using the command:
+Add [security configuration](../security/authentication) using the command:
 
 ```shell
 cds add xsuaa --for production

guides/deploy/to-cf.md

@@ -150,7 +150,7 @@ cds add xsuaa
 ```
 
 ::: tip This will also generate an `xs-security.json` file
-The roles/scopes are derived from authorization-related annotations in your CDS models. Ensure to rerun `cds compile --to xsuaa`, as documented in the [_Authorization_ guide](../security/authorization#xsuaa-configuration) whenever there are changes to these annotations.
+The roles/scopes are derived from authorization-related annotations in your CDS models. Ensure to rerun `cds compile --to xsuaa`, as documented in the [_Security_ guide](../security/cap-users#xsuaa-roles) whenever there are changes to these annotations.
 :::
 
 [Learn more about SAP Authorization and Trust Management/XSUAA.](https://discovery-center.cloud.sap/serviceCatalog/authorization-and-trust-management-service?region=all){.learn-more}

guides/playbook.drawio.svg

@@ -1,9 +1,13 @@
-# [SAP Product Standards](../../../guides/security/product-standards) <!-- INTERNAL -->
-# [CAP-level Authorization](authorization)
-# [Platform Security](platform)
-# [Data Protection](data-protection)
-# [Data Privacy](data-privacy)
+
+# [Security Overview](overview)
+# [Authentication](authentication)
+# [CAP Users](cap-users)
+# [CAP Authorization](authorization)
+# [Remote Authentication](remote-authentication)
+# [Data Privacy Overview](data-privacy)
 # [Annotating Personal Data](dpp-annotations)
 # [Automatic Audit Logging](dpp-audit-logging)
 # [Personal Data Management](dpp-pdm)
   <!-- ## [Data Retention Management](dpp-drm) -->
+# [Product Security Overview](data-protection)
+# [Product Security Standard](../../../guides/security/product-standards) <!-- INTERNAL -->