From b72e6382a8f7c8e94e688c4739e5dcd92dc5eca9 Mon Sep 17 00:00:00 2001 From: Lukas Eder Date: Thu, 21 Nov 2024 16:32:14 +0100 Subject: [PATCH] [jOOQ/jOOQ#9506] Could also be a bug --- jOOQ/src/main/java/org/jooq/impl/MigrationImpl.java | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/jOOQ/src/main/java/org/jooq/impl/MigrationImpl.java b/jOOQ/src/main/java/org/jooq/impl/MigrationImpl.java index bec7db1de9..17b550628b 100644 --- a/jOOQ/src/main/java/org/jooq/impl/MigrationImpl.java +++ b/jOOQ/src/main/java/org/jooq/impl/MigrationImpl.java @@ -258,9 +258,11 @@ final class MigrationImpl extends AbstractScope implements Migration { """ Non-empty difference between actual schema and migration from schema: {queries}. - This can happen for two reasons: + This can happen for at least 3 reasons: 1) The migration specification of a version that has already been installed has been modified. 2) The database schemas contain untracked objects. + 3) There's a false positive reported by the database / org.jooq.Meta. Please consider reporting + it here: https://jooq.org/bug Possible remedies if 1): - Revert changes to the migration specification and move those changes to a new version.