From a91d0a7d5e0730778b95a7e4cb67b2238349b97f Mon Sep 17 00:00:00 2001 From: Matthias Schur <107557548+MattSchur@users.noreply.github.com> Date: Tue, 31 Mar 2026 11:21:52 +0200 Subject: [PATCH] Avoid multi-exposing Elements in views --- java/working-with-cql/query-execution.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/java/working-with-cql/query-execution.md b/java/working-with-cql/query-execution.md index 1ad96cc9d5..b2f7a32a68 100644 --- a/java/working-with-cql/query-execution.md +++ b/java/working-with-cql/query-execution.md @@ -289,6 +289,10 @@ UPDATE entity OrderView2 Path expressions navigating *associations* (*header.customer.name*) are [not writable](#cascading-over-associations) by default. To avoid issues on write, annotate them with [@readonly](../../guides/services/constraints#readonly). ::: + ::: warning Avoid multi-exposing Elements via Aliases + Expose an element only once: either remove the original from the projection or annotate the alias with [@readonly](../../guides/services/constraints#readonly) to avoid write conflicts. + ::: + ### Delete through Views { #delete-via-view } The CAP Java runtime attempts to resolve [deletes](./query-api#delete) on CDS views to the underlying persistence entity definitions and the [write through views](#updatable-views) restrictions apply accordingly.