Repository navigation
pgCompare 0.7.0
This release focuses on SQL Server correctness fixes and security-relevant JDBC
driver updates.
Bug Fixes
-
SQL Server binary columns no longer silently skipped (#101)
castBinary()now emitsHASHBYTES('MD5', ...)(lowercase hex) for SQL Server
instead of falling through to Postgresmd5(), which SQL Server rejects. SQL
Serverrowversioncolumns (reported by the JDBC driver astimestamp) are now
routed to binary handling instead of being treated as temporal values. Previously
anybinary/varbinary/rowversionsource column aborted the source query and
the table was skipped with no error surfaced (source_cnt = 0). -
False numeric drift on non-English SQL Server sessions (#102)
castNumber()now pins theen-USculture on SQL ServerFORMAT()calls.
Previously, culture-aware formatting on non-English sessions (e.g. pt-BR, es-ES,
de-DE) produced comma decimal separators while the Postgres target produced a
period, causing every numeric column to report as out-of-sync. Output is
byte-identical on English sessions. -
checkno longer fails permanently after a delete between passes (#103)
compareRowforCheck()now handles the case where a row is absent on both source
and target (a delete landing betweencompareandcheck). This is treated as
convergence and the finding is cleared, rather than throwing
Array index out of range: 0and leaving the table permanently out-of-sync.
Dependency Updates
net.snowflake:snowflake-jdbc4.0.1 → 4.3.4 (addresses CVE-2026-3293 and CVE-2026-85528)com.microsoft.sqlserver:mssql-jdbc13.2.1.jre11 → 13.6.0.jre11com.ibm.db2:jcc12.1.3.0 → 12.1.5.0org.postgresql:postgresql42.7.10 → 42.7.13org.json:json20251224 → 20260814
Upgrade Notes
- No repository schema changes since 0.6.0; no re-initialization required.
- The Snowflake JDBC upgrade is recommended for all users on security grounds.