Storing the initial state
Though you could hand-roll the initial state if you prefer, we generally advise
that you take a schema-only dump of your existing (production) database schema
and store it to migrations/initial_schema.sql with a command such as:
pg_dump --schema-only --no-owner --file=migrations/initial_schema.sql "postgres://..."
If you want to change selection, open document below and click on "Move attachment"
GitHub - graphile/migrate: Opinionated SQL-powered productive roll-forward migration tool for PostgreSQL.ll databases (development, staging, production, etc.) are at the same state before running any migrations, and then the Graphile Migrate migrations will be applied on top of this initial state. <span>Storing the initial state Though you could hand-roll the initial state if you prefer, we generally advise that you take a schema-only dump of your existing (production) database schema and store it to migrations/initial_schema.sql with a command such as: pg_dump --schema-only --no-owner --file=migrations/initial_schema.sql "postgres://..." If you manage some of the data in your initial database schema using your existing migration system then you should add that data to your initial_schema.sql file too. New databases must Summary
| status | not read | | reprioritisations | |
|---|
| last reprioritisation on | | | suggested re-reading day | |
|---|
| started reading on | | | finished reading on | |
|---|
Details