3 ms·

One of Bytebase authors here, we use "state-based" and "declarative" https://www.bytebase.com/blog/database-version-control-state-based-vs-migration-based/ http

One of Bytebase authors here, we use "state-based" and "declarative" https://www.bytebase.com/blog/database-version-control-state-based-vs-migration-based/ https://www.bytebase.com/blog/database-version-control-state... interchangeably Our initial launch does use "state-based", but we later change it to "declarative". You can check the product here https://demo.bytebase.com/project/blog-102#gitops https://demo.bytebase.com/project/blog-102#gitops Of course, it's always a bit confusing to have multiple ways to reference the same thing. So be it.

evanelias 3y ago
I was referring to blog posts, for example [1], in which you admittedly use both terms in the text, but you focus more on "state-based" for example in the headline and image. You also erroneously conflate declarative migrations with somehow involving `mysqldump` for some reason? This is what I mean when I say posts like this feel like they're designed to make declarative migrations seem strange and foreign. I realize this post is two years old, and you're understandably not going to mention a competing product like mine. But it feels like a disingenuous strawman argument to claim that declarative schema management requires `mysqldump`, considering that Skeema (my product) and SQLDef (another declarative tool) were both released in 2016 and are both widely used. [1] https://www.bytebase.com/blog/database-version-control-state-based-vs-migration-based/ https://www.bytebase.com/blog/database-version-control-state...
- tianzhou 3y ago
  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.

evanelias 3y ago

I was referring to blog posts, for example [1], in which you admittedly use both terms in the text, but you focus more on "state-based" for example in the headline and image. You also erroneously conflate declarative migrations with somehow involving `mysqldump` for some reason? This is what I mean when I say posts like this feel like they're designed to make declarative migrations seem strange and foreign. I realize this post is two years old, and you're understandably not going to mention a competing product like mine. But it feels like a disingenuous strawman argument to claim that declarative schema management requires `mysqldump`, considering that Skeema (my product) and SQLDef (another declarative tool) were both released in 2016 and are both widely used. [1] https://www.bytebase.com/blog/database-version-control-state-based-vs-migration-based/ https://www.bytebase.com/blog/database-version-control-state...

tianzhou 3y ago
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.