能否通过Liquibase从现有数据库生成变更日志？单表对应单个XML文件

Absolutely—Liquibase has you covered here. You don’t have to settle for a single monolithic changelog file when you want each database table’s schema in its own XML file. Here’s a step-by-step breakdown of how to make this happen:

• Get your setup in order first
  Ensure Liquibase is installed, your database connection is configured (either via liquibase.properties or command-line arguments), and you have the correct JDBC driver for your database (MySQL, PostgreSQL, SQL Server, etc.) available.

• Generate changelogs one table at a time
  The key here is using Liquibase’s --includeObjects flag to target individual tables with the generateChangeLog command. For example, if you have a table named customers, run:

  liquibase generateChangeLog --includeObjects=table:customers --outputFile=changelog-customers.xml
  

  Just repeat this command for every table in your database, updating the table name and output file name each time. Each resulting XML file will only contain the schema definition (like the CREATE TABLE statement, plus any associated constraints for that table) for the specific table you targeted.

• Automate the process for large databases
  If you’ve got dozens of tables, doing this manually is tedious. Write a quick script (shell, PowerShell, or even a Python script) to:

  1. Pull a list of all tables from your database (the query varies by database—for PostgreSQL, it’s SELECT table_name FROM information_schema.tables WHERE table_schema = 'public';)
  2. Loop through each table name
  3. Run the generateChangeLog command automatically for each table, naming the output file something like changelog-[table-name].xml

• Tweak the output as needed
  If you want to exclude certain cross-table objects (like foreign keys that reference other tables, or shared indexes) from individual table files, add the --excludeObjects flag. For example:

  liquibase generateChangeLog --includeObjects=table:orders --excludeObjects=foreignkey,index --outputFile=changelog-orders.xml
  

  Just note that if you exclude cross-table dependencies, you might need to handle those in a separate changelog or ensure you apply your per-table files in the correct order later.

This approach works across all databases Liquibase supports, so you can use it regardless of what database you’re working with.

内容的提问来源于stack exchange，提问作者thomas