Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix deploymentId not populating after locking #4450

Merged
merged 2 commits into from
Jun 29, 2023
Merged

Fix deploymentId not populating after locking #4450

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c059d8c
Test to validate that DEPLOYMENT_ID is populated on update
wwillard7800 Jun 28, 2023
97903f5
[#4448] Ensure deploymentId is generated after waiting for lock.
abrackx Jun 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 4 additions & 0 deletions ...-integration-tests/src/test/groovy/liquibase/command/UpdateCommandsIntegrationTest.groovy
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,6 +58,10 @@ class UpdateCommandsIntegrationTest extends Specification {
resultSet.next()
resultSet.getInt(1) == 1

def detailsResultSet = h2.getConnection().createStatement().executeQuery("select DEPLOYMENT_ID from databasechangelog")
detailsResultSet.next()
assert detailsResultSet.getString(1) != null : "No deployment ID found for the update"

def rsTableExist = h2.getConnection().createStatement().executeQuery("select count(1) from example_table")
rsTableExist.next()
rsTableExist.getInt(1) == 0
Expand Down