You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RULES.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ Some are applicable for different technologies.
51
51
| GCI67 | Use the $i++ variable during an iteration | The $i++ form has the disadvantage of generating a tem-porary variable during incrementation, which is not the case with the ++$i form. |[cnumr best practices (3rd edition) BP_067 (no longer exists in edition 4)](https://www.greenit.fr/2019/05/07/ecoconception-web-les-115-bonnes-pratiques-3eme-edition/)| ✅ | ✅ | 🚀 | 🚫 | 🚫 | 🚫 | 🚫 |
52
52
| GCI69 | Calling a loop invariant function in a loop condition | Avoid calling loop invariant functions in loop conditions. |[cnumr best practices (3rd edition) BP_069 (no longer exists in edition 4)](https://www.greenit.fr/2019/05/07/ecoconception-web-les-115-bonnes-pratiques-3eme-edition/)| ✅ | ✅ | 🚀 | 🚫 | 🚀 | ✅ | 🚫 |
53
53
| GCI72 | Perform an SQL query inside a loop | Servers are optimized to process multiple selections, insertions, or changes in a single query or transaction. consume CPU cycles, RAM, and bandwidth unnecessarily. |[cnumr best practices (3rd edition) BP_072](https://github.com/cnumr/best-practices/blob/main/chapters/BP_072_fr.md)| ✅ | ✅ | 🚀 | ✅ | 🚀 | ✅ | 🚫 |
54
-
| GCI74 | Write SELGCIT * FROM | The database server must resolve the fields based on the schema. If you are familiar with the diagram, it is strongly recommended to name the fields. |[cnumr best practices (3rd edition) BP_074 (no longer exists in edition 4)](https://www.greenit.fr/2019/05/07/ecoconception-web-les-115-bonnes-pratiques-3eme-edition/)| ✅ | ✅ | 🚀 | ✅ | 🚀 | 🚀 | 🚫 |
54
+
| GCI74 | Write SELECT * FROM| The database server must resolve the fields based on the schema. If you are familiar with the diagram, it is strongly recommended to name the fields. |[cnumr best practices (3rd edition) BP_074 (no longer exists in edition 4)](https://www.greenit.fr/2019/05/07/ecoconception-web-les-115-bonnes-pratiques-3eme-edition/)| ✅ | ✅ | 🚀 | ✅ | 🚀 | 🚀 | 🚫 |
55
55
| GCI75 | Don't concatenate strings in loops | Avoid repeated string allocations and consider using a StringBuilder instead. || 🚫 | ❓ | ❓ | ❓ | ❓ | ✅ | 🚫 |
56
56
| GCI76 | Usage of static collections | Avoid usage of static collections. If you want to use static collections make them final and create for example a singleton if needed containing the collections. The static fields are more complicated for the Garbage Collector to manage and can lead to memory leaks. || ✅ | 🚫 | 🚫 | 🚫 | 🚫 | 🚫 | 🚫 |
57
57
| GCI77 | Usage Pattern.compile() in a non-static context | Avoid using Pattern.compile() in a non-static context. This operation requires a non negligible amount of computational power, Using a single match saves CPU cycles and RAM consumption. || ✅ | 🚫 | 🚫 | 🚫 | 🚫 | 🚫 | 🚫 |
0 commit comments