Gajus Kuizinas
1 min readAug 30, 2019

--

I don’t have this problem and struggle to understand why anyone would. Perhaps our development environments are very different. In my case, we have development environment where all the changes are being made ad-hoc (using CLI or whatever GUI tool to modify schema). Then when development environment needs to be deployed to production we identify the changes that were made (e.g. using https://www.postgrescompare.com/ or https://github.com/djrobstep/migra) and run the queries required to bring the two databases in sync (these tools generate migration queries for you). Regularly we delete development environment and re-create it by cloning production and removing sensitive data (e.g. PI customer date) using a hand-crafted procedure in the database.

What is your use case for “migration scripts” in this/ similar setup?

That being said, this was discussed before in this thread. https://github.com/gajus/slonik/issues/42

--

--

Gajus Kuizinas
Gajus Kuizinas

Written by Gajus Kuizinas

Founder, engineer interested in JavaScript, PostgreSQL and DevOps. Follow me on Twitter for outbursts about startups & engineering. https://twitter.com/kuizinas

Responses (1)