Skip to content

DEV: SetStore backed implementation of requires_set #33626

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

Merged
merged 2 commits into from
Jul 28, 2025
Merged

Conversation

s3lase
Copy link
Contributor

@s3lase s3lase commented Jul 15, 2025

This change updates requires_set internals to use our custom set implementations via Migrations::SetStore

@github-actions github-actions bot added the migrations-tooling PR which includes changes to migrations tooling label Jul 15, 2025
@s3lase s3lase force-pushed the dev/mt/requires-set branch from 6eccf6a to 7ec25bc Compare July 16, 2025 13:35
@s3lase s3lase marked this pull request as ready for review July 16, 2025 13:44
@s3lase s3lase requested a review from gschlager July 21, 2025 15:48
Base automatically changed from mt/set_store to main July 24, 2025 10:11
@s3lase s3lase force-pushed the dev/mt/requires-set branch from 7ec25bc to c1c3ed1 Compare July 24, 2025 11:51
s3lase added 2 commits July 25, 2025 14:11
This change updates requires_set` internals to use our custom
set implementations via `Migrations::SetStore`
Change `DiscourseDB#query_result` implementation to yield value
for single column query results instead of a single element array
@s3lase s3lase force-pushed the dev/mt/requires-set branch from c1c3ed1 to 62971c6 Compare July 25, 2025 17:35
@s3lase s3lase merged commit 57a04e7 into main Jul 28, 2025
6 checks passed
@s3lase s3lase deleted the dev/mt/requires-set branch July 28, 2025 10:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
migrations-tooling PR which includes changes to migrations tooling
Development

Successfully merging this pull request may close these issues.

2 participants