codd
codd copied to clipboard
mzabani
Codd is a simple-to-use CLI tool that applies plain postgres SQL migrations with strong and automatic cross-environment schema equality checks
Right now codd will create codd_schema before the first migration with the default connection string, meaning a dump that is used as a migration will also try to create codd_schema...
If one updates postgres, they currently need to coordinate a PR to upgrade the expected schema. It will be simpler if we put one folder per major PG version in...
Say one wants to add a new column to a table and populate it gradually, and they want to index it but not pay the price of locking the table...
The main use case that brought me to create this issue is that it would be outstanding if we could restore a large dump while skipping copying a hypothetical `logs`...
## The problem Because of session settings, migrations do not compose well. Suppose there are two migrations: Mig A: ````sql SET ROLE otherrole; ```` Mig B: ````sql CREATE TABLE sometbl();...
This is currently done manually: after I trigger the `Release` github workflow, I need to build the statically linked executable on my own computer and attach it to the github...
From https://github.com/mzabani/codd/issues/139, but from my own experience as well, it's clear users will want to customise schema equality checks and some times even what codd writes to disk for representations....
The Codd representation of a PostgreSQL function/procedure includes the MD5 hash of the source code of the function body when the function is implemented in SQL or PL/pgSQL ([reference][]). This...
Study the possibility of adding a new "vacuum-only" migration modifier that: 1 - Ensures DB checksums do not change and data is not deleted/inserted/updated 2 - Allows pre-commit checksum verifications...