C1 (3 points)
https://knobit.org/id/task/dq-sbvr-rule-anomalies/C1
Also as Turtle · JSON-LD · RDF/XML
| dcterms:license | https://creativecommons.org/licenses/by/4.0/ |
|---|---|
| rdfs:label | C1 (3 points) en |
| schema:hasPart | dq-sbvr-rule-anomalies C1a: foreign key on Delta Lake not trusted as enforcement |
| schema:hasPart | dq-sbvr-rule-anomalies C1b: change-over-time rule classified as data-update with a mechanism |
| schema:hasPart | dq-sbvr-rule-anomalies C1c: enforced PostgreSQL foreign key and Delta CHECK kept as constraints |
| schema:identifier | C1 |
| schema:position | 1 |
| schema:text | Enforcement as each platform actually provides it, 1 each: (a) BR-120 claims enforcement constraint through fk_interest_accrual_deposit, a FOREIGN KEY on Delta Lake, where primary and foreign keys are informational and not enforced - reported, and BR-120 becomes dq-check (or etl) with the DQ rule or load check recorded under physical_changes; (b) BR-107 (the principal must not change after opening) is a data-update rule (subtype prohibition), not data-content range, and no declarative constraint can enforce it - enforcement becomes application (e.g. a BEFORE UPDATE trigger), etl or dq-check, naming what implements it; (c) BR-105 (a PostgreSQL foreign key) and BR-121 (a Delta Lake CHECK constraint, which Delta does enforce) stay on enforcement constraint - this part earns its point only if (a) is also earned. en |