Repository navigation
Conversation
…reSQL Migration 0008 failed with "operator does not exist: text = uuid" on PostgreSQL databases migrated through 0003. The 0003 stubs declare forge_instance_id without the relation that gives fresh databases a uuid column, so those databases have text columns that 0008 can neither compare with nor constrain to forge_instances.id. Convert them first. Fixes cloudbase#920
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Migration 0008 fails with
operator does not exist: text = uuidon PostgreSQL databases that were migrated through 0003. On those databases,forge_instance_idinforge_instance_events,poolsandworkflow_jobsistext, while fresh databases getuuid. See #920.On PostgreSQL, 0008 now converts those columns to
uuidbefore its cleanup, so both the orphan cleanup and the foreign key creation work. Columns that are alreadyuuidare left alone, so fresh databases are unaffected. SQLite is untouched.TestConstraintParityOnPostgresnow builds its pre-constraint database withtextcolumns and a danglingforge_instance_id. Without the fix it fails with the same error we hit in production.Fixes #920