on 05-21-2022 1:17 PM
Hello CAP Documentation Team,
with the Release March 2022 the feature of Database Integrity Constraints was introduced. It is controlled by the configuration cds.env.features.assert_integrity. In the release Documentation you mention this possible values:
db
: Database constraintsapp
: Runtime checks (default, only effective in Node.js runtime)off
: No database constraints and no runtime checksBut in the documentation @assert.integrity Constraint for to-one Associations the value is mentioned as:
cds.env.features.assert_integrity = false
.
Is off and false doing the same? Maybe we consolidate to false.
Best Regards
Gregor
CC: iwona.hahn
Hi gregorw,
We have updated the documentation based on your feedback. Thank you for your contribution.
Best regards,
Iwona
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
11 | |
8 | |
8 | |
6 | |
6 | |
6 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.