Fix #1562 invalid update sql generated for hsql

[devorgpl]

---

name: Pull Request
about: #1562 fixes invalid update sql generated fof hsql
title: ''
labels: Status:Discovery
assignees: ''

---

Environment

Liquibase Version: all

Liquibase Integration & Version: all

Liquibase Extension(s) & Version:

Database Vendor & Version: hsql

Operating System Type & Version: all

Pull Request Type

• Bug fix (non-breaking change which fixes an issue.)
• Enhancement/New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

add table name and where clause to generated sql

Steps To Reproduce

Actual Behavior

Expected/Desired Behavior

Screenshots (if appropriate)

If applicable, add screenshots to help explain your problem.

Additional Context

Add any other context about the problem here.

Fast Track PR Acceptance Checklist:

• Build is successful and all new and existing tests pass
• Added Unit Test(s)
• Added Integration Test(s)
• Documentation Updated

Need Help?

Come chat with us on our discord channel

---

Dev Handoff Notes (Internal Use)

Links

• Fixed Issue: Invalid update SQL generated for HSQL database in InsertOrUpdateGeneratorHsql.java #1562
• Local Branch: https://github.com/liquibase/liquibase/tree/devorgpl-fix-1562
• Unit Tests: https://github.com/liquibase/liquibase/pull/1563/checks
• Integration Tests: (shown in Unit Tests link above)
• Functional Tests: https://jenkins.datical.net/job/liquibase-pro/job/devorgpl-fix-1562/

Testing

• Steps to Reproduce: Invalid update SQL generated for HSQL database in InsertOrUpdateGeneratorHsql.java #1562
• Guidance:
  • Only impacts loadUpdateData on hsql

Dev Verification

(did not save output from the time)

┆Issue is synchronized with this Jira Story by Unito

[molivasdat]

Hi @devorgpl
Thanks for fixing this.
And thanks for your pull request and additional unit test!

Here’s what happens next:

A member of the Liquibase team will take a look at your contribution and may suggest:

• Changes based on guidelines for PR submission
• Additional tests (unit and/or integration)
• Provide other feedback, like requesting changes.

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.