You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- As an AI bot reviewing documentation pull requests on GitHub, please focus on the following areas to ensure high-quality and effective documentation:
28
28
- Use U.S. English spelling and punctuation.
29
29
- Check for spelling errors and provide corrections.
30
30
- Identify and correct grammatical errors and incorrect punctuation.
31
31
- Provide suggestions for improving the clarity and conciseness of the text to make it more understandable. Use the comments to create real suggestions and include all proposals that target the same line into one suggestions. Do not create multiple suggestions for the same line or paragraph.
32
-
- Consider the guidelines that can be found in .github/workflows/assets/editor.md and apply them.
33
32
- Ensure that the tone is appropriate for technical documentation, maintaining a professional and informative style.
34
33
- Verify that the structure of the document is logical and that headings and subheadings are used effectively.
35
34
- Check for consistency in terminology and style throughout the document.
Copy file name to clipboardExpand all lines: guides/databases/cdl-to-ddl.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Databases are deployed based on the entity definitions in your CDS models. This
15
15
16
16
CDS compilation to database-specific DDLs is handled by the `cds compile` command, which is part of the [`cds` CLI](../../tools/cds-cli). When you run `cds deploy` or `cds watch`, this command is invoked automatically to generate the necessary DDL statements for your target database.
17
17
18
-
You can also run the command manually to see the generated DDL for your models. For example, to inspect what the SQL DDL for your entire model would look like, simply run:
18
+
You can also run the command manually to view the generated DDL for your models. For example, to inspect what the SQL DDL for your entire model would look like, simply run:
> CDS models are designed to be database-agnostic, allowing you to switch between different databases with minimal changes. The `--dialect` option helps you see how your models translate to different database-specific DDLs. \
61
+
> CDS models are designed to be database-agnostic, allowing you to switch between different databases with minimal changes. The `--dialect` option shows how your models translate to different database-specific DDLs. \
62
62
63
63
64
64
### Dialects by `cds env` Profiles
@@ -676,7 +676,7 @@ When using `@cds.persistence.exists` for ...
676
676
- User-defined functions (UDFs), annotate it with `@cds.persistence.udf` in addition.
677
677
- Calculation views, annotate it with `@cds.persistence.calcview` in addition.
678
678
679
-
See[Calculated Views and User-Defined Functions](./hana-native#calculated-views-and-user-defined-functions) for more details.
679
+
Refer to[Calculated Views and User-Defined Functions](./hana-native#calculated-views-and-user-defined-functions) for more details.
680
680
:::
681
681
682
682
@@ -736,7 +736,7 @@ CREATE VIEW ListOfBooks AS SELECT ... FROM Books WITH DDL ONLY;
736
736
-`@sql.prepend` is only supported for entities translating to tables. It can't be used with views or with elements.
737
737
738
738
> [!note] Note for SAP HANA
739
-
> Ensure to read[Schema Evolution Support of Native Database Clauses](hana#schema-evolution-native-db-clauses) if you plan to use these annotations in combination with [`@cds.persistence.journal`](hana#enabling-hdbmigrationtable-generation).
739
+
> Ensure to review[Schema Evolution Support of Native Database Clauses](hana#schema-evolution-native-db-clauses) if you plan to use these annotations in combination with [`@cds.persistence.journal`](hana#enabling-hdbmigrationtable-generation).
740
740
741
741
> [!caution]
742
742
> The content of these annotations is inserted as-is into the generated DDL statements without any validation or other processing by the compiler. Use this feature with caution, as incorrect SQL clauses may lead to deployment failures or runtime errors. You're responsible to ensure that the resulting statement is valid and doesn't negatively impact your database or your application. **We don't provide support for problems caused by using this feature.**
0 commit comments