You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proposal is to enable goose to drop the current database schema. This is usually done with tools like pg_dump.
Now, this would require the user to have this executable in their $PATHor we can invoke a lightweight container such as postgres:14-alpine, if neither is available then fail.
I don't think this should live inside the github.com/pressly/goose/v3 package, and instead should be its own subdir package, such as pgutil or something. I imagine we should expose a few of these mysqlutil. (can't come up with a better name, suggestions welcome to not use {dialect}util)
In the goose binaries, the behaviour could be to dump a schema file after running a modifying migration. The file could be written to the same folder as -dir as schema.sql
The text was updated successfully, but these errors were encountered:
mfridman
changed the title
Add functionality to dump database schema
feature: add functionality to dump database schema
Oct 16, 2021
The proposal is to enable
goose
to drop the current database schema. This is usually done with tools likepg_dump
.Now, this would require the user to have this executable in their
$PATH
or we can invoke a lightweight container such aspostgres:14-alpine
, if neither is available then fail.I don't think this should live inside the github.com/pressly/goose/v3 package, and instead should be its own subdir package, such as
pgutil
or something. I imagine we should expose a few of thesemysqlutil
. (can't come up with a better name, suggestions welcome to not use{dialect}util
)In the
goose
binaries, the behaviour could be to dump a schema file after running a modifying migration. The file could be written to the same folder as-dir
asschema.sql
The text was updated successfully, but these errors were encountered: