-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
ref(saved search): Migrate betterPriority to priority #52909
Conversation
This PR has a migration; here is the generated SQL for --
-- MIGRATION NOW PERFORMS OPERATION THAT CANNOT BE WRITTEN AS SQL:
-- Raw Python operation
-- |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #52909 +/- ##
=======================================
Coverage 79.37% 79.37%
=======================================
Files 4932 4934 +2
Lines 207130 207222 +92
Branches 35392 35405 +13
=======================================
+ Hits 164407 164489 +82
- Misses 37691 37701 +10
Partials 5032 5032
|
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.
30k rows in this table, should be safe to run as part of the deploy
Change references to the new priority sort to just "priority" for simplicity and to prevent more saved searches being created with the sort string "betterPriority". After this is merged we'll run a migration to make all saved searches for priority sort the same (#52909) and then finish by cleaning up the backend to only accept "priority" (right now it treats betterPriority and priority the same". Step 1: This PR Step 2: Migration #52909 Step 3: Backend PR #52915
Now that we've GA'd the new priority sort, we should clean up the saved searches that were made with the sort "betterPriority".
Step 1: Front end PR to stop saving searches w/ betterPriority #52910
Step 2: This PR
Step 3: Backend PR #52915