To avoid bothering learning how it operates behind the scenes, can developers and DBA use it by taking a snapshot of how a database looks right now, then make some changes in the database, and then having it snapshot again to see what changed, and then even record that?
Vague thoughts there, but the point I’m trying to make is, is it possible to use this app without learning the changelog XML stuff? Just allow a developer or DBA to make the changes in a database (local copy or whatever) and have the tool find them and save its changelog whatever it needs to apply those changes.
We’d use it only to output the SQL anyway, so we wouldn’t really care what it uses to track changes internally. Just want to actually do a change in a dev copy of a database, and have it eventually output the SQL to duplicate that change.