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
Currently each time a migration is applied and unless pgmgr dump is executed there's no dump or structure file that gets generated.
This feature would create a structure only sql file each time a migration is ran and can be toggled on and off via the config file through the setting:
{
"db-structure": "path/to/structure/"
}
By default, the structure is not generated unless this part of the configuration is specified.
The text was updated successfully, but these errors were encountered:
Hey, sorry for the delay in responding. We already have a config key, dump-file, to indicate where DB dumps (aka structure.sql) go, but what we don't have is a flag to automatically run it after migrating. In a production environment, that behavior is undesirable, but I can see use cases where you'd want it. Perhaps a "dump-after-migrate": true flag instead?
Currently each time a migration is applied and unless
pgmgr dump
is executed there's no dump or structure file that gets generated.This feature would create a structure only sql file each time a migration is ran and can be toggled on and off via the config file through the setting:
By default, the structure is not generated unless this part of the configuration is specified.
The text was updated successfully, but these errors were encountered: