(PC-38929)[API] refactor: optimize product counts update queries #20525
Conversation
This file contains hidden or 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
3b538d5 to
c7db614
Compare
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.
🎯 Related Ticket or 🔧 Changes Made
Ticket Jira
Avant on mettait à jour tous les produits, même ceux qui avaient déjà la bonne valeur.
Ici l'optimisation réside principalement dans l'ajout d'un
having(likesCount != count)pour ne traiter que les produits qui ont besoin d'un update.Donc les fonctions
_chronicles_count_query,_headlines_count_query,_likes_count_queryretournent désormais directement les données nécessaires à la fonctionfetch_inconsistent_product