I've set up some tables in DB Connect, using a timestamp (date_modified) as a rising column (there were no other suitable fields, and it's COTS, so the vendor isn't going to add a unique value). The where column is "where date_modified > ?".
The issue is that each time the input is run, it creates a new event for the most recent row. I would expect that to happen is the where clause said "where date_modified >= ?", but with it set as "where date_modified > ?", I would think it would just add no rows.
Has anyone else seen this?
I forgot to mention, I'm seeing this issue with tables that have a unique id as the rising column as well.