×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Handling Record Change Journal Entries, (continued)
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
