JHipster entity classes ↔ Liquibase changelog: Ensuring rollback safety after schema changes

Direct Answer

JHipster does not provide automatic <rollback> blocks for complex schema changes. The framework emits forward‑only migrations (e.g., addColumn, createTable) and leaves complex operations such as renameColumn, dropColumn, or foreign‑key adjustments without explicit rollback logic. Developers must insert the <rollback> tags manually.

Confirmed Facts

• Basic operations (addColumn, createTable) are automatically reversible by Liquibase.
• Complex operations require explicit <rollback> blocks to be reversible.
• JHipster has no built‑in toggle to generate exhaustive rollback sections.
• Manual edits can be overwritten when entities are regenerated; version control is essential.

Recommended Pattern

1. Generate the changelog: Run ./mvnw liquibase:base (or the npm equivalent) to produce the forward migration.
2. Identify non‑automatic changes: Look for renameTable, renameColumn, dropColumn, addForeignKeyConstraint, or custom sql tags.
3. Append rollback logic:

   <changeSet id="rename_user_table" author="jhipster">
     <renameTable tableName="user_old" newTableName="user"/>
     <rollback>
       <renameTable tableName="user" newTableName="user_old"/>
     </rollback>
   </changeSet>

4. Validate locally: Apply the changelog, then run liquibase rollback-count 1 or use liquibase update-sql and liquibase rollback-sql to inspect generated SQL.
5. Commit changes: Store the edited changelog under version control to avoid accidental loss.

Verifying Across Liquibase Versions

Liquibase 4.x added implicit rollback support for some operations that 3.x did not. To ensure compatibility:

• Run liquibase update-sql and liquibase rollback-sql for your target version.
• Compare the output against the Liquibase documentation for that version.
• If a rollback fails, add an explicit <rollback> block or adjust the change set.

Missing Diagnostic Detail

Which Liquibase major version(s) are you targeting? Rollback behavior differs between 3.x and 4.x, especially for renames and custom SQL.