From 7f5ec4f36c4a08389cc3b5be8de555469b8dbea9 Mon Sep 17 00:00:00 2001 From: Wout Date: Tue, 7 Mar 2023 08:58:33 +0100 Subject: [PATCH] Change typo in default end date changed `9999-31-12` to `9999-12-31` --- docs/tutorial/tut_eff_satellites.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tutorial/tut_eff_satellites.md b/docs/tutorial/tut_eff_satellites.md index 03dd942..692163d 100644 --- a/docs/tutorial/tut_eff_satellites.md +++ b/docs/tutorial/tut_eff_satellites.md @@ -14,7 +14,7 @@ A Link does not have any temporal data; it declares that there is a relationship To solve this, we create an Effectivity Satellite from `LINK_A_B` called `EFF_SAT_A_B`. This contains information about the status of `LINK_A_B`. Now we have two columns, `START_DATE` and `END_DATE`. When the Effectivity Satellite record is created, we set the `START_DATE` and leave the `END_DATE` empty, or in our case set it to the maximal date of -`9999-31-12` to signify that the relationship will not expire - it is active, or 'open'. +`9999-12-31` to signify that the relationship will not expire - it is active, or 'open'. Now imagine, the foreign key link in Table A changes for some reason, pointing to another record in Table B. The foreign key column in the row changes to point to the new record and it no longer points to the old record. This @@ -185,4 +185,4 @@ The resulting Effectivity Satellite table will look like this: | . | . | . | . | . | . | . | 1 | | D8CB1F... | FED333... | 8FAA77... | 1993-01-01 00:00:00.000 | 9999-31-12 00:00:00.000 | 1993-01-01 00:00:00.000 | 1993-01-01 00:00:00.000 | 1 | ---8<-- "includes/abbreviations.md" \ No newline at end of file +--8<-- "includes/abbreviations.md"