Re: Handling Record Change Journal Entries

[Don Brown <DBrown@xxxxxxxxxx>]

Rob, I would be interested in that presentation if you are sharing ?


Don Brown
 



From:   "Rob Berendt" <rob@xxxxxxxxx>
To:     "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date:   05/01/2019 04:06 AM
Subject:        Re: Handling Record Change Journal Entries
Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



With temporal tables you do add a few columns.  And this can have 
ramifications, depending on your application software (with record level 
checks).

But, if the application software is done right you can add those columns 
and not have an issue.
Let's take Infor LX for example.  Some might say they are not a shining 
example of good database definitions.  No primary keys, constraints, etc. 
However their LF's are done right.  They list every column individually 
and use a separate record format.
R IPR100CO                  PFILE(RCO       ) 
  CRSTS          1A         TEXT('Record Status') 
                            COLHDG('Rcd' + 
                                   'Sts' ) 
  CRTYP          1A         TEXT('Record Type') 
                            COLHDG('Rcd' + 
                                   'Typ' ) 
  CMPNY          2P 0       TEXT('Company Number')
                            COLHDG('Cmp' + 
                                   'Nbr' ) 
                            EDTCDE(X) 
...

So I played with this RCO file and used ALTER TABLE to add a few columns 
needed (or desired) for temporal table support.  Then I did the rest of 
the stuff needed for temporal table support.  I was able to run their 
software unchanged, no recompiles, without a single problem.

I have a presentation on this I can share offline.



Rob Berendt