fix(channel-web): fix messaging tables schema in channel-web migration #5760
Conversation
This file contains 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
DEV-2190 Fix not null constraint on providerId in msg_clients
The table schema for This would cause users which tables were created during the migration to have a |
laurentlp
deleted the
llp_fix_channel_web_mig_messaging_tables_schema
branch
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR fixes an issue where the table schema for
msg_clientscreated by the channel-web migration of 12.26.0 differs from the one defined by the Messaging server.This would cause users which tables were created during the migration to have a
not nullconstraint on theproviderIdcolumn that would result in issues when syncing with Messaging. The issue would only happen when you create or upload a bot with the same name as an old (deleted) bot.Closes DEV-2190
Type of change