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
We are using soda in an automated deployment scenario and we are running into issues with the schema that is output after a migrate up. Currently there is no way to prevent the owner of tables from being dumped to the schema.sql file, and we may have deployments where the owner varies per instance. It would be great if there was a way to extent the below function to include other postgresql pg_dump options:
As a workaround, we've added migrations/schema.sql to .gitignore, and on CI we always force migrations to run instead of loading from the schema.sql e.g.
We are using soda in an automated deployment scenario and we are running into issues with the schema that is output after a migrate up. Currently there is no way to prevent the owner of tables from being dumped to the schema.sql file, and we may have deployments where the owner varies per instance. It would be great if there was a way to extent the below function to include other postgresql pg_dump options:
The text was updated successfully, but these errors were encountered: