Drop one_team_per_user constraint from team_memberships
#5004
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
zoldar
force-pushed
the
drop-one-team-per-user-constraint
branch
from
80e01bb to
a978a90
Compare
10 tasks
zoldar
force-pushed
the
autocreated-teams
branch
2 times, most recently
from
42e38cf to
b466339
Compare
zoldar
force-pushed
the
drop-one-team-per-user-constraint
branch
from
a978a90 to
66c2123
Compare
|
aerosol
approved these changes
Jan 29, 2025
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.
Changes
Dropping that constraint opens capability to support meany team meberships per user and many owner user per team.
This migration also sets
team_memberships.is_autocreatedvalue back tofalsefor consistency.Depends on #5003