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
And you may want to track the migrations for them separate that is you will run db-migrate up only for the public schema or you will run db-migrate up only for the analytics schema
Not sure if this makes sense at all. Is there a way to make this work?
db-migrate only current supports migration sequence for one schema that means
migrations/20111219120005-create-owners-table.js
migrations/20111220890005-create-shops-table.js
This is fine if you only have one schema in the database to manage
In a scenario where you have multiple schema
e.g.
You may have 2 sets of schemas:
migrations/public/20111219120005-create-owners-table.js
migrations/public/20111220890005-create-shops-table.js
migrations/analytics_schema/20111219120007-create-owners-analytics-view.js
migrations/analytics_schema/20111240890005-create-shops-analytics-view.js
And you may want to track the migrations for them separate that is you will run
db-migrate up
only for the public schema or you will rundb-migrate up
only for the analytics schemaNot sure if this makes sense at all. Is there a way to make this work?
Schema: http://www.postgresql.org/docs/9.3/static/sql-createschema.html
The text was updated successfully, but these errors were encountered: