3 ms·

We stated the reality at the time of writing that migration-based approach is more common. I think that still holds true today. Meanwhile, there are more soluti

We stated the reality at the time of writing that migration-based approach is more common. I think that still holds true today. Meanwhile, there are more solutions introducing the state-based solution (including Bytebase itself). >> it feels like a disingenuous strawman argument to claim that declarative schema management requires `mysqldump` The article explicitly said it's a hybrid approach and never intended to claim this way. Otherwise, it would be an obvious mis-statement.

evanelias 3y ago
> We stated the reality at the time of writing that migration-based approach is more common. Yes, and I have not disputed this at any point here. > The article explicitly said it's a hybrid approach and never intended to claim this way. Otherwise, it would be an obvious mis-statement. Your blog post said "State-based approach stores the desired end state of the entire schema in the code repository. For MySQL, it means to store the schema dump created by mysqldump." I think that is indeed an obvious mis-statement. It would give a casual unfamiliar reader the impression that declarative schema management somehow involves/requires mysqldump.