fix: remove unique username constraint (hotfix) - #1290
Merged
Conversation
jekabs-karklins
requested review from
deepaksftc
and removed request for
a team
December 11, 2025 09:51
simonfernandes
approved these changes
Dec 11, 2025
gnyiri
approved these changes
Dec 11, 2025
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
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 removes the unique username constraint from the users table in the backend.
Motivation and Context
The unique username constraint was causing issues with an ongoing integration. The field username is proposed to be removed in PR #1126
Changes
0202_DropUsersUsernameKey.sqlto remove the unique username constraint from the public.users table.How Has This Been Tested?
Locally making sure it workd properly
Fixes Jira Issue
https://jira.esss.lu.se/browse/
Depends On
Tests included/Docs Updated?