After the previous changes we select the max ts from a history table to determine what the max timestamp should be. However, when the table is empty this query returns null, which causes repeated extractions to fail. This change instead has the value default to the set max timestamp, instead of returning null in this case.
Type of change
Please delete options that are not relevant.
[ ] Bug fix (non-breaking change which fixes an issue)
How Has This Been Tested?
Added a new test and tested manually against both the running test db and a db here at cox auto.
Description
After the previous changes we select the max ts from a history table to determine what the max timestamp should be. However, when the table is empty this query returns null, which causes repeated extractions to fail. This change instead has the value default to the set max timestamp, instead of returning null in this case.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Added a new test and tested manually against both the running test db and a db here at cox auto.