Kai Lochbaum
2018-11-13 16:09:05 UTC
Hi everyone,
over the years we have accumulated lots of migration versions in multiple models (one at 66, another at 54).
Did anyone ever think about some sort of consolidation to make the initial migration on a fresh database quicker?
I was thinking of something like a âskipToVersionâ method where you would update your 0-Migration with the most current database model and add a skipToVersion(66) call at the end, so that ERXMigration directly skips from 0 to 66.
Cheers,
Kai Lochbaum
over the years we have accumulated lots of migration versions in multiple models (one at 66, another at 54).
Did anyone ever think about some sort of consolidation to make the initial migration on a fresh database quicker?
I was thinking of something like a âskipToVersionâ method where you would update your 0-Migration with the most current database model and add a skipToVersion(66) call at the end, so that ERXMigration directly skips from 0 to 66.
Cheers,
Kai Lochbaum
--
Telefon: 069 / 65 00 96 - 17 | E-Mail: ***@salient-doremus.de<mailto:***@salient-doremus.de>
salient GmbH, LindleystraÃe 12, 60314 Frankfurt
Telefon Zentrale: 069 / 65 00 96 - 0 | http://www.salient-doremus.de<http://www.salient-doremus.de/>
Telefon: 069 / 65 00 96 - 17 | E-Mail: ***@salient-doremus.de<mailto:***@salient-doremus.de>
salient GmbH, LindleystraÃe 12, 60314 Frankfurt
Telefon Zentrale: 069 / 65 00 96 - 0 | http://www.salient-doremus.de<http://www.salient-doremus.de/>