-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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.
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
database changelog history record-keeping (DAT-16178) #5147
Conversation
…s from factory (DAT-15985) (#5123)
@@ -23,7 +25,7 @@ | |||
return results; | |||
} | |||
|
|||
public int getExitCode() { | |||
public Integer getExitCode() { |
Check notice
Code scanning / CodeQL
Missing Override annotation Note
ExitCodeException.getExitCode
private static final long serialVersionUID = 1570124571347160550L; | ||
private Integer exitCode = null; |
Check notice
Code scanning / CodeQL
Missing Override annotation Note
ExitCodeException.getExitCode
return null; | ||
} | ||
|
||
public static class LibraryInfo implements Comparable<LibraryInfo> { |
Check warning
Code scanning / CodeQL
Inconsistent compareTo Warning
compareTo
…ing history table (DAT-15973) (#5203)
@@ -7,4 +7,7 @@ | |||
public interface ChangeLogSyncListener { | |||
void markedRan(ChangeSet changeSet, DatabaseChangeLog databaseChangeLog, Database database); | |||
|
|||
default void markedRanFailed(ChangeSet changeSet, DatabaseChangeLog databaseChangeLog, Database database, Exception e) { |
Check notice
Code scanning / CodeQL
Useless parameter Note
@@ -7,4 +7,7 @@ | |||
public interface ChangeLogSyncListener { | |||
void markedRan(ChangeSet changeSet, DatabaseChangeLog databaseChangeLog, Database database); | |||
|
|||
default void markedRanFailed(ChangeSet changeSet, DatabaseChangeLog databaseChangeLog, Database database, Exception e) { |
Check notice
Code scanning / CodeQL
Useless parameter Note
@@ -7,4 +7,7 @@ | |||
public interface ChangeLogSyncListener { | |||
void markedRan(ChangeSet changeSet, DatabaseChangeLog databaseChangeLog, Database database); | |||
|
|||
default void markedRanFailed(ChangeSet changeSet, DatabaseChangeLog databaseChangeLog, Database database, Exception e) { |
Check notice
Code scanning / CodeQL
Useless parameter Note
@@ -7,4 +7,7 @@ | |||
public interface ChangeLogSyncListener { | |||
void markedRan(ChangeSet changeSet, DatabaseChangeLog databaseChangeLog, Database database); | |||
|
|||
default void markedRanFailed(ChangeSet changeSet, DatabaseChangeLog databaseChangeLog, Database database, Exception e) { |
Check notice
Code scanning / CodeQL
Useless parameter Note
Kudos, SonarCloud Quality Gate passed! |
@@ -83,6 +89,11 @@ | |||
resultsBuilder.addResult("statusCode", 0); | |||
} | |||
|
|||
public SnapshotControl getSnapshotControl(CommandScope commandScope, Database database) { |
Check notice
Code scanning / CodeQL
Useless parameter Note
@@ -83,6 +89,11 @@ | |||
resultsBuilder.addResult("statusCode", 0); | |||
} | |||
|
|||
public SnapshotControl getSnapshotControl(CommandScope commandScope, Database database) { |
Check notice
Code scanning / CodeQL
Useless parameter Note
…5375) add dbcl-history configuration options to maven plugin
# Conflicts: # liquibase-standard/src/main/java/liquibase/command/CommandScope.java # liquibase-standard/src/main/java/liquibase/database/Database.java
# Conflicts: # liquibase-cli/src/main/java/liquibase/integration/commandline/LiquibaseCommandLine.java
add maven arguments to scope
…en (DAT-16881) (#5609) fix dbclHistoryEnabled property from liquibase.properties file in maven
record executed SQL in ChangelogJdbcMdcListener
default void addCompleteSqlToScope(String completeSql) { | ||
AtomicReference<String> sqlsReference = Scope.getCurrentScope().get(COMPLETE_SQL_SCOPE_KEY, AtomicReference.class); | ||
if (sqlsReference != null) { | ||
sqlsReference.set(completeSql.toString()); |
Check notice
Code scanning / CodeQL
Useless toString on String Note
…0) (#5651) * add captureExtensions and captureSql params to maven plugin * update javadoc * additional javadoc fixes
Impact
Description
The current DBCL tracks changes currently applied to a db, but when changes are rolledback, these changeset records dissappear. This new PRO table, DATABASECHANGELOGHISTORY, will track all changes made and rolled back and dropped. The overall goal of this table is track the history of database changing liquibase operations, including rollbacks, dropall, repeated updates of the same changeset, etc.
Things to be aware of
Things to worry about
Additional Context