Request: Incremental loading with millisecond precision timestamps

[nixnut]

I ran into a problem with timestamps with millisecond precision. Due to the floating point numbers of Qlik I need to add a fraction to the max timestamp retrieved from the incremental qvd to make avoid falling victim to rounding errors and loading some records twice from both the source database and the incremental qvd:

current:

• LET _vDate.Max = replace(peek('Qvc.MaxModFieldValue'), '$(DecimalSep)', '.'); // Ensure using "." as decimal sep

requested:

• LET _vDate.Max = replace(rangesum(pow(2,-26),peek('Qvc.MaxModFieldValue')), '$(DecimalSep)', '.'); // Ensure using "." as decimal sep

[RobWunderlich]

Sorry for the delay in addressing this one. "loading some records twice from both the source database and the incremental qvd". In my opinion, this is normal behavior when using timestamps. The timestamp comparison is always ">=" and it is expected to retrieve the same row as the max. The row should then be filtered by "where not exists(pk)"

[RobWunderlich]

Closing to due to no activity