CRJVM205 - Forcer l'utilisation du FetchType LAZY sur les collections… #155
+168
−21
Conversation
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
… dans les Entity JPA
|
Kudos, SonarCloud Quality Gate passed! |
Open
|
Duplicates #125 |
|
Duplicates #122 |
MP-Aubay
added
🗃️ rule
|
This PR has been automatically marked as stale because it has no activity for 30 days. |
This was referenced Aug 25, 2023
|
This PR has been automatically marked as stale because it has no activity for 30 days. |
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.
Le FetchType LAZY est une stratégie de récupération de données utilisée dans les relations de type OneToMany ou ManyToMany, où les données associées ne sont chargées qu'au moment où elles sont effectivement utilisées.
Il est recommandé d'utiliser FetchType LAZY pour les collections car cela permet d'améliorer les performances de l'application en évitant de charger des données qui ne seront pas utilisées. Cela peut également éviter des problèmes de mémoire pour les collections contenant un grand nombre d'éléments.