Add safe decimal migration tooling#397
Merged
kilodesodiq-arch merged 1 commit intoJul 21, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes #238.
Adds safe Float-to-Decimal migration tooling for money-like database columns. The script supports dry-run row counts, NaN/Infinity preflight rejection, gzipped JSONL backups,
pg_dump --data-onlysafety backups, single-transaction conversion toNUMERIC, sentinel-based idempotency, and rollback restore from backup archives.Also adds a database migration runbook and an npm script entry:
I did not run the migration against a live PostgreSQL database because no DATABASE_URL was provided.
Screenshots
Not applicable.
Checklist