We have adopted widespread use of System Time functionality on our application tables. We have need to use transparent archiving as well, since we have table where data churn is significant and we don't have need to track row changes - just the final state of the row once it's removed from the processing table.
However, we discovered recently a limitation that disallows referencing both a System Time temporal table and a transparent archiving enabled table in the same SQL statement. With our widespread use of system time, this essentially blocks our ability to use transparent archiving, as there will almost always be a join between tables of these two types.
I know one solution is to use system time with the 'ON DELETE ADD EXTRA ROW' option instead of transparent archiving; however, the two functions work differently and for different reasons. As stated above, we don't need the additional functionality that system time provides.
This was a shocking find and I'm not sure I understand why the two features won't work together. A significant limitation.
Why is it useful?
|Who would benefit from this IDEA?|
How should it work?
|Customer Name||State of WI - Dept of Workforce Development|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions