-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add migration to add existing group creators as owners #9031
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
51 changes: 51 additions & 0 deletions
51
h/migrations/versions/59f42b6a0cd9_add_group_creators_as_owners.py
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
"""Add existing group creators as owners.""" | ||
|
||
from alembic import op | ||
from sqlalchemy import Column, ForeignKey, Integer, MetaData, Table, select, update | ||
from sqlalchemy.dialects.postgresql import JSONB | ||
|
||
metadata = MetaData() | ||
|
||
|
||
user_table = Table("user", metadata, Column("id", Integer, primary_key=True)) | ||
|
||
|
||
group_table = Table( | ||
"group", | ||
metadata, | ||
Column("id", Integer, primary_key=True), | ||
Column("creator_id", Integer, ForeignKey("user.id")), | ||
) | ||
|
||
|
||
user_group_table = Table( | ||
"user_group", | ||
metadata, | ||
Column("id", Integer, primary_key=True), | ||
Column("user_id", Integer, ForeignKey("user.id")), | ||
Column("group_id", Integer, ForeignKey("group.id")), | ||
Column("roles", JSONB), | ||
) | ||
|
||
|
||
revision = "59f42b6a0cd9" | ||
down_revision = "1975edef158d" | ||
|
||
|
||
def upgrade(): | ||
op.execute( | ||
update(user_group_table) | ||
.where( | ||
user_group_table.c.id.in_( | ||
select(user_group_table.c.id) | ||
.where(user_group_table.c.group_id == group_table.c.id) | ||
.where(user_group_table.c.user_id == user_table.c.id) | ||
.where(user_table.c.id == group_table.c.creator_id) | ||
) | ||
) | ||
.values(roles=["owner"]) | ||
) | ||
|
||
|
||
def downgrade(): | ||
pass |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not all existing groups will have creators. There are three cases:
"group".creator_id
isNULL
. There's nothing to do in this case."group".creator_id
will still correspond to an existing"user".id
but there will be nouser_group
row with a matchinggroup_id
anduser_id
. Again there's nothing to do in this case.user_group
row and updateroles
to["owner"]
.And of course we need to not update
user_group
roles for non-creator memberships.I'm hoping I can get away with updating all the rows at once as in the SQL query above. In the production DB there are 191,571 rows matching:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm hoping we can get away with updating all the rows at once as in the SQL query above. In the production DB there are 191,571 rows matching:
I reckon it would be fine but we should run it early in the morning just in case.