v0.12.5

This release introduces an important change on how intervals worked in ingestr.

Important - Closed Intervals

This release introduces a change in how --interval-start and --interval-end works in ingestr. Previously, these flags were treated as [interval-start, interval-end), meaning that the values with interval-start would be included, the ones with interval-end would be excluded, which means the ranges would not be overlapping.

In more tangible terms, the previous version would create a query like this to get the data based on an updated_at field:

SELECT *
FROM mytable
WHERE updated_at >= :interval_start AND updated_at < :interval_end

In the new version, this is how the query looks like:

SELECT *
FROM mytable
WHERE updated_at >= :interval_start AND updated_at <= :interval_end

This means certain bits of data will be fetched unnecessarily, but ingestr will deduplicate the data anyway. This is especially helpful for date-based incremental keys where there's no high-precision timestamp available.

Full Changelog: v0.12.4...v0.12.5