4 ms·
This page doesn't really demonstrate the product well. There are links to some other pages that show somewhat more complicated changes, but they still don't dem
by caymanjim 6y ago
This page doesn't really demonstrate the product well. There are links to some other pages that show somewhat more complicated changes, but they still don't demonstrate any complex transformations or migrations. Maybe it can do these things; if so, and the author wants to sell people on its capabilities, they should be front and center.
XML is a non-starter for most people. I know this is a Java product, and Java developers have a perverse love affair with XML, but literally no one else uses it. The page mentions that changesets can be written in JSON and YAML, but there are no examples. XML is a horrid abomination and I have a viscerally negative reaction to seeing it. At least show something that doesn't cause PTSD to the viewer.
I've used Rails DB migrations (written in Ruby with ActiveRecord's DSL), Alembic (written in Python with SQLAlchemy's DSL), and roll-my-own pure SQL, and nothing beats SQL. You're working with a database, why not work with its language? Any migration of significant complexity requires the use of actual SQL, and trying to abstract that away just results in mixing languages and obscuring the change being made. It only takes a few lines of code to manage the versioning.