WARNING: This project still lacks many features. It is not ready for production use yet. Please be noted some of the generated migrations are not safe to apply at this moment. If you have better ideas on how those migrations should be, please submit an issue.
Renovate is a CLI tool to help you to work on Postgres schema migration easily.
Example:
```console,ignore ➜ renovate schema init postgres://localhost:5432/test ➜ cat public/tables.sql CREATE TABLE public.todos (title text, completed boolean);⏎ ➜ cat > public/tables.sql CREATE TABLE public.todos (title text, completed boolean, created_at timestamptz default now()); ➜ renovate schema plan Table public.todos is changed:
1 |-CREATE TABLE public.todos (title text, completed boolean) 1 |+CREATE TABLE public.todos ( 2 |+ title text, 3 |+ completed boolean, 4 |+ created_at timestamptz DEFAULT NOW() 5 |+)
The following SQLs will be applied:
ALTER TABLE public.todos ADD COLUMN created_at timestamptz DEFAULT NOW(); ```
Renovate is inspired by terraform. It also tries to generate migration declaratively, not imperatively. Terraform invented a new language to describe the resources, but Renovate decides to just use the existing SQL DDL to do so. It is a bit tricky to generate the migration from the SQL DDL, but it is much easier to understand and maintain.
Under the hood, Renovate uses pgquery to parse the Postgres SQL DDL, and use pgdump to retrieve the remote state. After a Renovate repo is created (by calling renovate schema init), it will keep track of the local state and the remote state. When you run renovate schema plan, it will retrieve the local state from the repo and the remote state via pg_dump, then parse both as AST using pg_query, and compare the two ASTs to generate the migration. The below figure shows the workflow of Renovate:
For more information, see the initial thoughts. Or you can also check the architecture.
Currently, Renovate only support installation from source:
console,ignore
$ cargo install renovate
```console $ renovate schema ? 2 renovate-schema[..] Schema migration
USAGE:
renovate schema [OPTIONS]
OPTIONS: --drop-on-exit drop database on exit (for testing purpose only) -h, --help Print help information
SUBCOMMANDS: apply apply the migration plan to the remote database server fetch fetch the most recent schema from the remote database server help Print this message or the help of the given subcommand(s) init init a database migration repo normalize normalize local schema via a temp local database plan diff the local change and remote state, then make a migration plan
```
Q: what if my change to the schema is not supported?
A: Please submit an issue to let us know. We will try to support it as soon as possible. Meanwhile, you could manually apply that change to the remote database, then run renovate schema fetch to update the local state.
Q: Can I use Renovate as a library?
A: Yes, you can include it as a dependency in your project. Please exclude cli feature if you just want to use the core. But it is not recommended to use it as a library at this moment. The API is not stable yet.
Q: What is the plan or roadmap for Renovate? A: I don't have a roadmap now. I need to get as much feedback as possible from you. My priority, for now, is to make it stable and reliable. The project has a decent number of unit tests (57 unit tests + 1 CLI test) at the time of writing, but it still lacks coverage for many scenarios. I haven't produced any user guide yet, and it is important.