-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[PM-19128] - Optimize Update Collections #5626
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
[PM-19128] - Optimize Update Collections #5626
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5626 +/- ##
==========================================
+ Coverage 45.73% 48.82% +3.09%
==========================================
Files 1603 1603
Lines 72659 72659
Branches 6507 6507
==========================================
+ Hits 33229 35479 +2250
+ Misses 38018 35718 -2300
- Partials 1412 1462 +50 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Fixed Issues (4)Great job! The following issues were fixed in this Pull Request
|
|
shane-melton
left a comment
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.
We should look into moving the CollectionRepositoryTests file to AC ownership in the future.
rkac-bw
left a comment
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.
lgtm





🎟️ Tracking
PM-19128
📔 Objective
This updates the existing sproc to not use merge statements and also adds indices to the join tables
CollectionGroupandCollectionUser.📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:) or similar for great changes:memo:) or ℹ️ (:information_source:) for notes or general info:question:) for questions:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:) for suggestions / improvements:x:) or:warning:) for more significant problems or concerns needing attention:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt:pick:) for minor or nitpick changes