Skip to content
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

Document the absence of virtual elements in the Result #486

Closed
wants to merge 2 commits into from
Closed

Document the absence of virtual elements in the Result #486

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bb966d6
Document the absence of virtual elements in the Result
vmikhailenko Oct 17, 2023
9fd0f41
Better phrasing
vmikhailenko Oct 17, 2023
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
4 changes: 4 additions & 0 deletions java/migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -371,6 +371,10 @@ result.rowCount(2); // 0 matches with ID 0

The default value of CDS Property `cds.security.authentication.normalizeProviderTenant` is changed to `true`. With this change, the provider tenant is normalized and set to `null` in the UserInfo by default. If you have subscribed the provider tenant to your application you need to disable this feature.

#### Vitrual elements
vmikhailenko marked this conversation as resolved.
Show resolved Hide resolved

The values for elements annotated with the annotation `@Core.Computed: true`, notably, virtual elements are no longer retained after CQN statement execution. Previously this was the case only for `Upsert` statement. Their values are no longer available in the `Result` of the CQN statement and are not available in the `@After` handlers.

### Lean Draft

The property `cds.drafts.associationsToInactiveEntities` has been removed. It enabled a feature, which caused associations to other draft documents to combine active and inactive versions of the association target. This mixing of inactive and active data is no longer supported.
Expand Down