You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixed: exporting a binary/blob/bit column to SQL format (or a scheduled SQL
export) on MySQL or MSSQL produced a literal that re-imported as the wrong
bytes — sqlValueLiteral quoted the hex-encoded value as a plain string
('\xdeadbeef' on MySQL, N'\xdeadbeef' on MSSQL) instead of that engine's
binary-literal syntax (X'deadbeef', 0xdeadbeef), unlike the row-backup
restore and CSV import code paths which already handled this correctly.
Verified live against real MySQL and MSSQL containers: a VARBINARY
column now round-trips byte-for-byte through export → reimport.
Fixed: Cassandra's "Show DDL" for a table dropped DESC clustering order
entirely — it read the clustering column names but never their ClusteringOrder, so re-running the generated DDL silently recreated the
table with ascending order. Now emits WITH CLUSTERING ORDER BY (...).
Verified live against a real Cassandra container.
Fixed: the audit log's SHA-256 hash chain (tamper-evidence) was written
correctly but never verified — VerifyPreparedAudit existed but nothing
ever called it. Added Store.VerifyAuditChain, wired into a daily
background check (auditIntegrityCheck) that walks every organization's
chain and logs an error if an entry no longer matches what it was written
with. Verified with a direct-database tampering test.