FPSINPUT.BLD_CHGLOG

>

> FPSINPUT.WIP_WAFER_HIST_LOOP

View FPSADMIN.BLD_CHGLOG

This view builds the script to create or alter the CHGLOG tables and WRLOG triggers. It feeds ADM_SET_CHGLOG so all of this is done automatically. This seems like a good place for a note about why we have the next_chg_ts field in our CHGLOG tables. There are two reasons: 1) The value of null in this field indicates the current record. We could have put an is_curr_record flag instead of next_timestamp for this but either way we need an additional field and having next_timestamp allows for #2. 2) The simple query below gives a snapshot of the table at the time ts in the past. We could get this using lag or lead but that would be significantly slower: select * from xxx_chglog where ts between chg_timestamp and nvl(next_timestamp, sysdate);