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
I am considering using Goose for incremental database migrations.
One key requirement is the ability to export the final SQL schema, making it easier to verify the resulting database schema without directly exporting from the database.
If Goose does not support this feature, I would consider applying all migrations to a test database and exporting the schema from there.
I am looking forward to your response and appreciate any guidance you can provide. Any further discussions or suggestions can be discussed here.
The text was updated successfully, but these errors were encountered:
Not at the moment, I've been experimenting with a command to wrap pg_dump, but haven't made much progress. #459
This gets even trickier because we'd need to implement this for most or all databases we support. And as that number goes up the maintenance burden increases.
Most users typically apply all migrations and then use a dedicated tool, like pg_dump for postgres, to dump the schema.
There's an existing issue #278 tracking this request, so going to close this for now.
I am considering using Goose for incremental database migrations.
One key requirement is the ability to export the final SQL schema, making it easier to verify the resulting database schema without directly exporting from the database.
If Goose does not support this feature, I would consider applying all migrations to a test database and exporting the schema from there.
I am looking forward to your response and appreciate any guidance you can provide. Any further discussions or suggestions can be discussed here.
The text was updated successfully, but these errors were encountered: