Module conformance 

Engine-agnostic conformance checking.

This is the reusable logic the integration tests used to inline: run a dialect’s whole-table checksum SQL through an Engine, parse the single result row, and compare two sides. Because it speaks only the Engine / [Dialect] traits, it works for same-engine and cross-engine comparisons and carries no database-driver dependencies — the concrete engines live in the adapter crates (vrtb-pg, vrtb-duck), and the live tests that exercise real databases live in the CLI crate.

Structs

ChecksumResult

The fast-exit precheck tuple: row count plus the two 64-bit checksum halves (kept as decimal strings — they are unsigned 64-bit values that may exceed i64, and the engines already hand them back as text).

Enums

Verdict

Outcome of comparing two sides.

Functions

conformance_check

Checksum both sides (which may be backed by different engines) and compare. On a same-engine differ: stream differing keys (default) or, with materialize, write the full diff server-side into that table instead.

whole_table_checksum

Build the dialect’s whole-table checksum SQL, run it on engine, and parse the single (cnt, sum_h1, sum_h2) row it returns.