Fix #111: Filter lock table check by current_schema() for multi-schem… #112
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-schema support The YugabyteDB extension was checking for the existence of yb_flyway_lock_table across ALL schemas using information_schema.columns without filtering by schema. This caused issues when migrating multiple schemas: - First schema creates the lock table successfully - Subsequent schemas find the table exists (in another schema) and don't create their own - When trying to use the lock table, it fails because it's not in the current schema This fix adds 'AND table_schema = current_schema()' to the LOCK_TABLE_SCHEMA_SQL query, ensuring each schema checks for and creates its own independent lock table. Fixes flyway#111
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…a support
The YugabyteDB extension was checking for the existence of yb_flyway_lock_table across ALL schemas using information_schema.columns without filtering by schema. This caused issues when migrating multiple schemas:
This fix adds 'AND table_schema = current_schema()' to the LOCK_TABLE_SCHEMA_SQL query, ensuring each schema checks for and creates its own independent lock table.
Fixes #111