Using drizzle in single tenant applications
Our use case is that we have single tenant applications that are spun up per client, each with their own database. We want to use drizzle to generate a "fresh" database when it is provisioned.
Normally for existing databases, drizzle will generate new .sql files to alter columns, tables, etc, creating a time series sql steps to get to the happy current state of the db.
When spinning up a fresh database, it would be more efficient to run a generated .sql file that is just the end state. For example, a table with column "test1" that was renamed to "test2" would generate two .sql files, one to create the column as "test1" and one to alter table and rename to "test2". However, for a fresh database it would be ideal to just skip to creating the column as "test2" when you create the db.
Are there any commands or patterns for managing changes in a db as well as generating the final end state sql for new databases?
0 Replies