I5 (2 points)

https://knobit.org/id/task/dm-ddl-review-deploy/I5

dcterms:license	https://creativecommons.org/licenses/by/4.0/
owl:sameAs	https://bitbucket.org/reffa/ontology/id/task/dm-ddl-review-deploy/I5
rdfs:label	I5 (2 points) en
schema:hasPart	dm-ddl-review-deploy I5: mandatory foreign-key cycle taken as resolved
schema:identifier	I5
schema:position	8
schema:text	Foreign-key cycle taken as resolved, 1 each: (a) dim_account.primary_card_key -> dim_card and dim_card.account_key -> dim_account are both NOT NULL, so although the header says every foreign key is added afterwards as ALTER TABLE and the script runs, the first load has no row it can insert first; (b) the cycle is resolved in the logical model - one direction made optional, or the primary-card relationship moved to its own table or to a flag on dim_card - and the header note is treated as a prompt, not a solution (deferring constraints is not offered as the fix, since not every target can defer one). en

Used by

has question	Card and account mart DDL on five engines, with its release evidence (DDL review skills)
schema:isPartOf	dm-ddl-review-deploy I5: mandatory foreign-key cycle taken as resolved