From 327cb7ccfc2e73933925da121c3166af03293420 Mon Sep 17 00:00:00 2001 From: dc Date: Thu, 5 Sep 2024 11:32:00 +0200 Subject: [PATCH] fix: wording --- docs/dcc-tables.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/dcc-tables.md b/docs/dcc-tables.md index eb70bc9..ac21db6 100644 --- a/docs/dcc-tables.md +++ b/docs/dcc-tables.md @@ -49,7 +49,7 @@ This is a required field. The support for BITEMPORAL loads is restricted, in the sense it is only possible to load data at a single point in time (no support for loading _multiple_ business date ranges for a _specific_ BUSKEY). The workaround is simply to load each date range separately. As a result of this restriction, the EDIT page will only show the latest business date range for each key. To modify earlier values, a filter should be applied. !!! Warning - If your target table contains referential constraints (eg primary key values that are linked to a master table) then this will cause problems with the UPDATE and REPLACE load types. This is due to the fact these both involve delete operations. If removal of these constraints is not an option, the workaround would be to create a separate (mirror) table, and update that using PRE-EDIT and POST-APPROVE hook scripts. Please contact Data Controller support for advice / assistance. + If your target table contains referential constraints (eg primary key values that are linked to a child table with a corresponding foreign key) then this will cause problems with the UPDATE and REPLACE load types. This is due to the fact these both involve delete operations. If removal of these constraints is not an option, the workaround would be to create a separate (mirror) table, and update that using PRE-EDIT and POST-APPROVE hook scripts. Please contact Data Controller support for advice / assistance. ### BUSKEY