Skip to content

CRJVM205 - Forcer l'utilisation du FetchType LAZY sur les collections… - #155

Closed
kerimboukadida wants to merge 1 commit into
green-code-initiative:mainfrom
kerimboukadida:CRJVM205-java-4ko-UseFetchTypeLazyRule
Closed

CRJVM205 - Forcer l'utilisation du FetchType LAZY sur les collections…#155
kerimboukadida wants to merge 1 commit into
green-code-initiative:mainfrom
kerimboukadida:CRJVM205-java-4ko-UseFetchTypeLazyRule

Conversation

@kerimboukadida

Copy link
Copy Markdown

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.

@sonarqubecloud

sonarqubecloud Bot commented Apr 6, 2023

Copy link
Copy Markdown

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

92.9% 92.9% Coverage
0.0% 0.0% Duplication

@kerimboukadida

Copy link
Copy Markdown
Author

on a tester cette règle sur un projet

MicrosoftTeams-image (2)
MicrosoftTeams-image (1)
MicrosoftTeams-image

@MP-Aubay MP-Aubay mentioned this pull request Apr 6, 2023
@wokier

wokier commented Apr 6, 2023

Copy link
Copy Markdown

Duplicates #125

@wokier

wokier commented Apr 6, 2023

Copy link
Copy Markdown

Duplicates #122

@MP-Aubay MP-Aubay added 🗃️ rule rule improvment or rule development or bug java 🏆 challenge2023 🏆 Work done during the ecoCode Challenge 2023 labels Apr 7, 2023
@github-actions

Copy link
Copy Markdown
Contributor

This PR has been automatically marked as stale because it has no activity for 30 days.
Please add a comment if you want to keep the issue open. Thank you for your contributions!

@github-actions

Copy link
Copy Markdown
Contributor

This PR has been automatically marked as stale because it has no activity for 30 days.
Please add a comment if you want to keep the issue open. Thank you for your contributions!

@github-actions github-actions Bot added the stale label Oct 23, 2023
@dedece35
dedece35 marked this pull request as draft March 9, 2025 15:26
@dedece35

dedece35 commented Mar 9, 2025

Copy link
Copy Markdown
Member

I marked this PR as draft because of duplication (see above)

@github-actions github-actions Bot removed the stale label Mar 10, 2025
@github-actions

Copy link
Copy Markdown
Contributor

This PR has been automatically marked as stale because it has no activity for 60 days.
Please add a comment if you want to keep the issue open. Thank you for your contributions!

@dedece35

dedece35 commented Aug 7, 2026

Copy link
Copy Markdown
Member

Hi @kerimboukadida , @wokier

several PR have worked on this same subject (FetchType Lazy instead of Eager for OneToMany et ManyToMany relations).

After worked on a complete analysis to check if this rule is relevant :

  • first, I found that the rule already exists in SonarQube as a built-in rule : S6904
  • secondly, no proof was found to check relevancy
  • thirdly, I decided to launch an analysis with EnergyTracer tool which can do real measures

Thus I created a new PR to :

  • add this analysis
  • clean all old references to this same subject

Here is the PR : #487

Sorry, but I have to close this PR.
thank you for the work.

@dedece35 dedece35 removed the stale label Aug 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🗃️ rule rule improvment or rule development or bug 🏆 challenge2023 🏆 Work done during the ecoCode Challenge 2023 duplicate This issue or pull request already exists java

Projects

Development

Successfully merging this pull request may close these issues.

4 participants