4 ms·
IMHO this is the opposite to the ideal approach. The current schema version should contain tables and the old schema versions should contain views. Using the cu
by aargh_aargh 5y ago
IMHO this is the opposite to the ideal approach. The current schema version should contain tables and the old schema versions should contain views. Using the current form of Reshape is asking for maintainability and performance problems down the road as its approach doesn't let you easily drop old schemas and change indexes as new needs emerge.
- fabianlindfors 5y agoThe old schemas will be automatically dropped when the migration is completed. So there will ever only be either one schema (current migration) or two during a deploy. I'm not sure what you mean by maintainability and performance. It's only during a migration that Reshape will add triggers and temporary tables and such. Once a migration is completed, the tables will look just like what you expect, no Reshape stuff. The only thing Reshape adds in between migrations are the schema and some views, nothing should build up over time.