Skip to content

(cds 9) Journal annotation is copied to generated child entities #1828

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

(cds 9) Journal annotation is copied to generated child entities #1828

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e2c59eb
(cds 9) Journal annotation is copied to generated child entities
stewsk May 8, 2025
baae068
Update guides/databases-hana.md
stewsk May 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions guides/databases-hana.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -508,6 +508,12 @@ Examples:

We recommend keeping _.hdbtable_ deployment for entities where you expect low data volume. Every _.hdbmigrationtable_ artifact becomes part of your versioned source code, creating a new migration version on every model change/build cycle. In turn, each such migration can require manual resolution.
You can switch large-volume tables to _.hdbmigrationtable_ at any time, keeping in mind that the existing _.hdbtable_ design-time artifact needs to be undeployed.

When choosing to use _.hdbmigrationtable_ for an entity with
[localized elements](../guides/localized-data#localized-data) or [compositions of aspects](../cds/cdl#managed-compositions),
the generated `.texts` and composition child entities are autmatically handled via _.hdbmigrationtable_, too.
If this is not desired, annotate these generated entities with `@cds.persistence.journal: false`.

::: tip
Sticking to _.hdbtable_ for the actual application development phase avoids lots of initial migration versions that would need to be applied to the database schema.
:::
Expand Down
Loading