Skip to Content
2
May 21, 2022 at 12:17 PM

Inconsistent documentation for assert_integrity

341 Views

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 constraints
  • app: Runtime checks (default, only effective in Node.js runtime)
  • off: No database constraints and no runtime checks

But 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