Fix missing catalog on add column rollback

[jandurovec]

When rollback script for "add column" change is generated, catalog name is missing from generated SQL. As a result of that the rollback may not work if the affected table is not in the default catalog.

[ro-rah]

Hi @jandurovec

Thanks for your pull request!

Here’s what happens next:

A member of the Liquibase team will take a look at your contribution and may suggest
changes, additional tests, or provide other feedback. The PR will be prioritized
according to our internal development and testing capacity.

We’ll let you know when it’s ready to move to the next step or if any changes are needed.

[ro-rah]

Adding Risk low as it fixes a break and includes unit tests

[github-actions]

Unit Test Results

  4 620 files  ±  0    4 620 suites  ±0   37m 53s ⏱️ +26s
  4 618 tests +  1    4 403 ✔️ +  5     215 💤  - 4  0 ❌ ±0 
54 588 runs  +12  49 568 ✔️ +16  5 020 💤  - 4  0 ❌ ±0 

Results for commit 337283a. ± Comparison against base commit e742a88.

♻️ This comment has been updated with latest results.

[nvoxland]

Code review and test results:

Things to be aware of:

• Changes make sense to me
• Added unit test to ensure data is being copied correctly

Things to worry about:

• Nothing

[XDelphiGrl]

This fix preserves the catalog name when generating drop column SQL.

• A new unit test validates the catalog, schema and table name are all included in a drop column statement.

APPROVED

[tabbyf00]

Thanks for your PR submission! We just finished reviewing and merging it into the 4.17.0 release on October 10, 2022. When you get a chance, could you please Star the Liquibase project? The star button is in the upper right corner of the screen.