Removed reliance of CREATE_HISTORY_CHANGES on the RESOLUTION value - it simply uses the source table's columns to determine this now. Might be possible to do something similar for CREATE_HISTORY_TRIGGERS in future
Removed reliance of CREATE_HISTORY_CHANGES on the RESOLUTION value - it simply uses the source table's columns to determine this now. Might be possible to do something similar for CREATE_HISTORY_TRIGGERS in future



waveform80/db2utils,waveform80/db2utils