Introduce correct error message when exceeding field length #712
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
samyuktaprabhu
force-pushed
the
sam-397-error-message-note
branch
from
79ab474 to
f170046
Compare
eric-pSAP
approved these changes
Jan 13, 2026
Schmarvinius
approved these changes
Jan 13, 2026
samyuktaprabhu
force-pushed
the
sam-397-error-message-note
branch
from
425a03f to
b0f4f84
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR: Enforce String length contract in CDS to prevent DB 500 errors
Previously, oversized String values relied on database defaults for validation (255 on SQLite/Postgres, 5000 on HANA), which caused DB constraint violations and HTTP 500 errors and also showed 'Error Executing the statement' without proper error message being displayed.
This PR has a change in CDS so that CAP validates input at the service boundary and returns a proper 400 Bad Request instead of leaking database errors. This follows a contract-first design and ensures consistent behavior across all databases.