Gülçin Yıldırım Jelinek

Thanks @ilyakooo0 for providing details, we'll look at it and get back to you.

Hi @ilyakooo0, let us know if the pointers shared by @kvch were helpful.

> Thanks for the pointers. > > [@gulcin](https://github.com/gulcin) My issue was initially not in updating initial migrations to fit the new schema. My issue was that there is no upgrade...

Hello @ilyakooo0, with the recent release of `pgroll v0.14` we introduced `pgroll update` command to help users to upgrade without needing to nuke their database 🙂 In your case, the...

> It defaults to postgres tools but the behavior is slightly different. Default postgres tools use the current logged in user AND respect [documented env vars](https://www.postgresql.org/docs/current/libpq-envars.html). > > `pgroll` has...

Hello @ericwooley, Thank you for these ideas, much appreciated! The workflow you described for `pgroll migrate --verify` is very much in line with what we plan to offer as part...

Thanks for providing feedback @maingoh, it gives us more clarity when we prioritize issues for upcoming releases. We tagged this as part of the `v1` milestone and will keep you...

Hello @ludat thank you for sharing your use case with us, we really appreciate the feedback! As you mentioned, the building blocks for this are already available: * You can...

Thanks @ludat for putting the details together in a table, really helpful. We'll keep this issue updated when we can work on this.

Hi @danzika nice see you here! In the event of a migration failure (e.g., network issues, VM crash), the migration remains in an "active" state. You can re-run `pgroll rollback`...