Hey there! Let's walk through your Liquibase questions step by step—since you already use Liquibase for table creation and data inserts, we'll stick to that native workflow you're comfortable with.

1. How to Configure Liquibase to Drop a Single Table #

Dropping a single table in Liquibase's YAML format is straightforward using the dropTable change type. To avoid errors if the table doesn't exist, just add the failOnError: false flag:

databaseChangeLog:
  - changeSet:
      id: drop-users-table
      author: your-name
      changes:
        - dropTable:
            tableName: users
            failOnError: false

• failOnError: false ensures Liquibase skips the operation quietly if the table isn't present. If you want a visible log message instead of silence, you can pair this with a precondition (we'll cover that approach in the next section).

2. Full Schema Drop with YAML + Liquibase (Skip if No Tables Exist) #

To fully wipe your schema without errors when no tables are present, and add clear feedback messages, we'll use preconditions to check for existing tables first. This way, we only run the drop operation when there's something to delete, and log a helpful message when we skip it.

Here's a complete, production-ready YAML example (replace public with your target schema name):

databaseChangeLog:
  - changeSet:
      id: full-schema-drop-if-tables-exist
      author: your-name
      preConditions:
        - sqlCheck:
            expectedResult: "1"
            # This query returns '1' if tables exist, '0' otherwise
            sql: |
              SELECT CASE 
                      WHEN COUNT(*) > 0 THEN '1' 
                      ELSE '0' 
                    END 
              FROM information_schema.tables 
              WHERE table_schema = 'public' 
                AND table_type = 'BASE TABLE'
        - onFail: MARK_RAN
        - onFailMessage: "No tables found in the 'public' schema. Skipping full drop operation."
      changes:
        - log:
            message: "Detected tables in 'public' schema. Starting full drop process..."
        - dropAll:
            schemaName: public
            dropSequences: true
            dropConstraints: true
        - log:
            message: "Successfully dropped all tables, sequences, and constraints in 'public' schema."

Let's break down what this does: #

• Precondition Check: The sqlCheck runs a query to detect if there are any base tables in your schema. It returns '1' if tables exist, so the precondition passes, and we run the drop steps. If no tables are found, it returns '0', the precondition fails.
• Skip & Log: onFail: MARK_RAN tells Liquibase to mark this changeSet as executed even when it skips the drop, so it won't re-run the check in future migrations. onFailMessage adds a clear log entry explaining why the drop was skipped.
• Full Schema Wipe: The dropAll change type handles removing all tables, sequences, and constraints in your specified schema (adjust dropSequences/dropConstraints to false if you don't want to remove those).
• Visibility: The log steps add clear feedback to your migration logs, so you can easily confirm whether the drop ran or was skipped.

If you need more granular control (like dropping specific objects instead of everything), you could replace dropAll with individual dropTable, dropSequence, etc., entries—each with failOnError: false—but dropAll is the most efficient way for a full schema wipe.

内容的提问来源于stack exchange，提问作者Евгений Когут