New folder guides/databases

Author: danjoa

about/features.md

@@ -197,12 +197,12 @@ Following is an index of the features currently covered by CAP, with status and
 
 |                                                                 | CDS/deploy | Node.js | Java |
 |-----------------------------------------------------------------|:----------:|:-------:|:----:|
-| [SAP HANA](../guides/databases)                                 |    <X/>    |  <X/>   | <X/> |
-| [SAP HANA Cloud](../guides/databases-hana)                      |    <X/>    |  <X/>   | <X/> |
-| [PostgreSQL](../guides/databases-postgres)                      |    <X/>    |  <X/>   | <X/> |
-| [SQLite](../guides/databases-sqlite) <sup>1</sup>               |    <X/>    |  <X/>   | <X/> |
+| [SAP HANA](../guides/databases/index)                                 |    <X/>    |  <X/>   | <X/> |
+| [SAP HANA Cloud](../guides/databases/hana)                      |    <X/>    |  <X/>   | <X/> |
+| [PostgreSQL](../guides/databases/postgres)                      |    <X/>    |  <X/>   | <X/> |
+| [SQLite](../guides/databases/sqlite) <sup>1</sup>               |    <X/>    |  <X/>   | <X/> |
 | [H2](../java/cqn-services/persistence-services#h2) <sup>1</sup> |    <X/>    |  <Na/>  | <X/> |
-| [MongoDB](../guides/databases) out of the box                   |   <Na/>    |  <Na/>  | <D/> |
+| [MongoDB](../guides/databases/index) out of the box                   |   <Na/>    |  <Na/>  | <D/> |
 | Pluggable drivers architecture                                  |    <D/>    |  <D/>   | <X/> |
 | Out-of-the-box support for other databases?                     |    <C/>    |  <C/>   | <C/> |
 

advanced/fiori.md

@@ -525,7 +525,7 @@ SELECT.from(Books.drafts) //returns all drafts of the Books entity
 
 In addition to adding [restrictions on services, entities, and actions/functions](/guides/security/authorization#restrictions), there are use cases where you only want to hide certain parts of the UI for specific users. This is possible by using the respective UI annotations like `@UI.Hidden` or `@UI.CreateHidden` in conjunction with `$edmJson` pointing to a singleton.
 
-First, you define the [singleton](../advanced/odata#singletons) in your service and annotate it with [`@cds.persistence.skip`](../guides/databases#cds-persistence-skip) so that no database artefact is created:
+First, you define the [singleton](../advanced/odata#singletons) in your service and annotate it with [`@cds.persistence.skip`](../guides/databases/index#cds-persistence-skip) so that no database artefact is created:
 
 ```cds
 @odata.singleton @cds.persistence.skip
@@ -861,4 +861,3 @@ extend AdminService.Genres with @(
 > `<entity name in service>Hierarchy`
 
 <div id="reserved-words" />
-

cds/annotations.md

@@ -63,14 +63,14 @@ uacp: Used as link target from Help Portal at https://help.sap.com/products/BTP/
 
 | Annotation                | Description                                                            |
 |---------------------------|------------------------------------------------------------------------|
-| `@cds.persistence.exists` | see [Generating DDL Files](../guides/databases#cds-persistence-exists) |
-| `@cds.persistence.table`  | see [Generating DDL Files](../guides/databases#cds-persistence-table)  |
-| `@cds.persistence.skip`   | see [Generating DDL Files](../guides/databases#cds-persistence-skip)   |
+| `@cds.persistence.exists` | see [Generating DDL Files](../guides/databases/index#cds-persistence-exists) |
+| `@cds.persistence.table`  | see [Generating DDL Files](../guides/databases/index#cds-persistence-table)  |
+| `@cds.persistence.skip`   | see [Generating DDL Files](../guides/databases/index#cds-persistence-skip)   |
 | `@cds.persistence.mock`   | `false` excludes this entity from automatic mocking                    |
 | `@cds.on.insert`          | see [Providing Services](../guides/providing-services)                 |
 | `@cds.on.update`          | see [Providing Services](../guides/providing-services)                 |
-| `@sql.prepend`            | see [Generating DDL Files](../guides/databases#sql-prepend-append)     |
-| `@sql.append`             | see [Generating DDL Files](../guides/databases#sql-prepend-append)     |
+| `@sql.prepend`            | see [Generating DDL Files](../guides/databases/index#sql-prepend-append)     |
+| `@sql.append`             | see [Generating DDL Files](../guides/databases/index#sql-prepend-append)     |
 
 ## OData
 

cds/cdl.md

@@ -858,7 +858,7 @@ Result result = service.run(Select.from("UsingView"), params);
 
 ### Runtime Views { #runtimeviews }
 
-To add or update CDS views without redeploying the database schema, annotate them with [@cds.persistence.skip](../guides/databases#cds-persistence-skip). This advises the CDS compiler to skip generating database views for these CDS views. Instead, CAP resolves them *at runtime* on each request. 
+To add or update CDS views without redeploying the database schema, annotate them with [@cds.persistence.skip](../guides/databases/index#cds-persistence-skip). This advises the CDS compiler to skip generating database views for these CDS views. Instead, CAP resolves them *at runtime* on each request. 
 
 Runtime views must be simple [projections](#as-projection-on), not using *aggregations*, *join*, *union* or *subqueries* in the *from* clause, but may have a *where* condition if they are only used to read.
 
@@ -948,7 +948,7 @@ This example is equivalent to the [unmanaged example above](#unmanaged-associati
 key element `address_ID` being added automatically upon activation to a SQL database.
 The names of the automatically added foreign key elements cannot be changed.
 
-> Note: For adding foreign key constraints on database level, see [Database Constraints.](../guides/databases#database-constraints).
+> Note: For adding foreign key constraints on database level, see [Database Constraints.](../guides/databases/index#database-constraints).
 
 If the target has a single primary key, a default value can be provided.
 This default applies to the generated foreign key element `address_ID`:
@@ -1429,7 +1429,7 @@ Propagation of annotations can be stopped via value `null`, for example, `@anno:
 :::
 
 
-### Expressions as Annotation Values {#expressions-as-annotation-values}
+### Expressions as Annotation Values
 
 In order to use an expression as an annotation value, it must be enclosed in parentheses:
 ```cds

cds/common.md

@@ -421,7 +421,7 @@ EU;European Union;European Union
 ```
 :::
 
-[Learn more about the database aspects of **Providing Initial Data**.](../guides/databases#providing-initial-data){ .learn-more}
+[Learn more about the database aspects of **Providing Initial Data**.](../guides/databases/index#providing-initial-data){ .learn-more}
 
 
 ### Add Translated Texts

cds/compiler/hdbcds-to-hdbtable.md

@@ -69,7 +69,7 @@ If the table doesn't contain much data, this process won't significantly impact
 
 ## Annotations
 
-Annotations [`@sql.append/prepend`](../../guides/databases#sql-prepend-append) are used to generate native SQL clauses to the _.hdbtable_ files, or add native SAP HANA CDS clauses to the _.hdbcds_ files.
+Annotations [`@sql.append/prepend`](../../guides/databases/index#sql-prepend-append) are used to generate native SQL clauses to the _.hdbtable_ files, or add native SAP HANA CDS clauses to the _.hdbcds_ files.
 
 If you have used these annotations in your model, a simple switchover from `hdbcds` to `hdbtable` is unlikely as such an annotation written for `hdbcds` in general is not valid for `hdbtable`. You'll have to adapt your model before the migration.
 

cds/compiler/v2.md

@@ -705,7 +705,7 @@ Select.from("bookshop.Books", b -> b.matching(id).to("texts"));
 
 #### CSV Files
 
-CAP Java allows to [provide initial data](../../guides/databases#providing-initial-data) to your application using CSV files. The name of the CSV file should adhere to the pattern `<namespace>-<entity>.csv` (`<qualified-entity-name>.csv`). Renaming the CSV file is recommended.
+CAP Java allows to [provide initial data](../../guides/databases/index#providing-initial-data) to your application using CSV files. The name of the CSV file should adhere to the pattern `<namespace>-<entity>.csv` (`<qualified-entity-name>.csv`). Renaming the CSV file is recommended.
 
 ```sh
 mv bookshop-Books_texts.csv bookshop-Books.texts.csv

get-started/in-a-nutshell.md

@@ -423,7 +423,7 @@ c.s.c.s.impl.persistence.CsvDataLoader   : Filling sap.capire.bookshop.Books fro
 
 </span>
 
-[Learn more about **Using Databases**.](../guides/databases){.learn-more}
+[Learn more about **Using Databases**.](../guides/databases/index){.learn-more}
 
 
 ### Querying via OData
@@ -491,7 +491,7 @@ cds deploy --to hana
 ```
 :::
 
-[Learn more about deploying to SAP HANA.](../guides/databases){.learn-more .impl .node}
+[Learn more about deploying to SAP HANA.](../guides/databases/index){.learn-more .impl .node}
 
 
 
@@ -831,7 +831,7 @@ With this getting started guide we introduced many of the basics of CAP, such as
 - [Domain Modeling](../guides/domain-modeling)
 - [Providing Services](../guides/providing-services)
 - [Consuming Services](../guides/using-services)
-- [Using Databases](../guides/databases)
+- [Using Databases](../guides/databases/index)
 - [Serving UIs](../advanced/fiori)
 
 Visit the [***Cookbook***](../guides/) for deep dive guides on these topics and more. Also see the reference documentations for [***CDS***](../cds/), as well as [***Node.js***](../node.js/) and [***Java***](../java/) Service SDKs and runtimes.

get-started/troubleshooting.md

@@ -510,7 +510,7 @@ After you have successfully deployed these changes to all affected HDI (tenant)
 |  | Explanation |
 | --- | ---- |
 | _Root Cause_ | Your configuration isn't properly set. |
-| _Solution_ | Configure your project as described in [Using Databases](../guides/databases).
+| _Solution_ | Configure your project as described in [Using Databases](../guides/databases/index).
 
 
 #### Deployment fails — _Connection failed (RTE:[89008] Socket closed by peer_ {#connection-failed-89008}

guides/data-privacy/annotations.md

@@ -144,7 +144,7 @@ Use this annotation to identify data subject's unique key, or a reference to it.
 - Each `@PersonalData` entity needs to identify a `DataSubjectID` element.
 - For entities with `DataSubject` semantics, this is typically the primary key.
 - For entities with `DataSubjectDetails` or `Other`  semantics, this is usually an association to the data subject.
-- Fields marked as `DataSubjectID` should use [`not null`](../databases#not-null) to guarantee a value is present at all times.
+- Fields marked as `DataSubjectID` should use [`not null`](../databases/index#not-null) to guarantee a value is present at all times.
 
 Hence, we annotate our model as follows: