I’d like to generate a changelog from an existing (pre liquibase) database and have the data exported in XML or Json, but it only seems to get produced in csv. Am I trying to do something that can’t (yet) be done?
Naturally, there’s no point having the data exported in something other than csv if it can’t be imported elsewhere later.
I have experimented with the --format option on the command line and have produced the schema change file in xml, but the data itself seems only to get exported in csv. Some of the data contains newlines and. as such, causes noticeable problems for trying to process the csv files. Whilst this isn’t a show-stopper, I’d really like to avoid having such problems at the start of this project.
The only time I got non-csv data was when one of the combination of options resulted in the insert statements being produced in SQL in the changelog file.
“The extension you provide determines the format of the changelog, so if you specify the filename as changelog.xml, you will get an XML formatted changelog. However, if you specify the filename as changelog.yaml, changelog.json, or changelog.sql, you will get changelogs formatted in YAML, JSON, or SQL, respectively.”
Thank you, daryldoak. I’ve noticed and experimented with that, already. It does indeed “what it says on the tin”, but this does not affect the format for the data that is being produced from the tables. This seems to always be in .csv formatted files - one per table.
I’m going to conclude that, at the moment, it is not possible.
