×
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.
No, you can set up temporal tables on existing applications. Just requires
a few steps and of course journaling.
Reasonably easy and if that solves the business requirement, then that is
the way I would go.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Richard
Schoen via MIDRANGE-L
Sent: Friday, January 04, 2019 11:52 AM
To: midrange-l@xxxxxxxxxxxx
Cc: Richard Schoen <Richard.Schoen@xxxxxxxxxxxxxxx>
Subject: Re: Handling Record Change Journal Entries
Actually in this case near-real-time is adequate I think.
I'll look at triggers as well. There could be several tables and I don't
like glomming on to unknown app tables without knowing ramifications.
With the temporal stuff does that assume you're creating all new tables for
your apps ?
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 3
date: Fri, 4 Jan 2019 12:45:31 -0500
from: Rob Berendt <rob@xxxxxxxxx>
subject: Re: Handling Record Change Journal Entries
"real time"
I would think this would be a better fit for a trigger.
If you just want to log the changes then using the 7.3 temporal table stuff
ROCKS!
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/rzahf/rzahftemporal
table.htm
Rob Berendt
midrange.com
