Sync documentation updates from cakephp-docs-md

  🤖 Generated with GitHub Actions from 2025-10-24 02:33:29 UTC

  Co-Authored-By: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Author: github-actions[bot]

docs/5.x/appendices/5-0-migration-guide.md

@@ -212,39 +212,30 @@ changes made:
 
 ### Known Issues
 
-**Memory Usage with extract() on Large Result Sets**
+**Memory usage with large result sets**
 
-When using `extract()` on large query results, you may experience higher memory
-usage compared to CakePHP 4.x. The collection iterator may materialize the entire
-result set into memory instead of processing results lazily.
+Compared to CakePHP 4.x, when working with large data sets (especially when
+calling collection methods like `extract()` on the result set), you may encounter
+high memory usage due to the entire result set being buffered in memory.
 
-If you encounter memory issues when extracting values from large result sets,
-use one of these workarounds:
-
-**Option 1: Disable hydration and iterate manually**:
+You can work around this issue by disabling results buffering for the query:
 
 ``` php
-$query = $articles->find()
-    ->select(['id'])
-    ->disableHydration();
-
-foreach ($query as $row) {
-    $id = $row['id'];
-    // Process each value
-}
+$results = $articles->find()
+    ->disableBufferedResults()
+    ->all();
 ```
 
-**Option 2: Build your list while iterating**:
+Depending on your use case, you may also consider using disabling hydration:
 
 ``` php
-$query = $articles->find()->select(['id', 'title'])->disableHydration();
-
-$ids = [];
-foreach ($query as $row) {
-    $ids[] = $row['id'];
-}
+$results = $articles->find()
+    ->disableHydration()
+    ->all();
 ```
 
+The above will disable creation of entity objects and return rows as arrays instead.
+
 ### Routing
 
 - Static methods `connect()`, `prefix()`, `scope()` and `plugin()` of the `Router` have been removed and

docs/5.x/orm/retrieving-data-and-resultsets.md

@@ -1060,38 +1060,27 @@ done with result sets using the collections features. The [Format Results](../or
 section show how you can add calculated fields, or replace the result set.
 
 > [!WARNING]
-> When working with large datasets, `extract()` may materialize the entire
-> result set into memory. If you encounter memory issues with large queries,
-> consider these alternatives:
+> When working with large data sets (especially when calling collection methods
+> like `extract()` on the result set), you may encounter high memory usage
+> due to the entire result set being buffered in memory.
 >
-> **Option 1: Use disableHydration() with manual extraction**:
+> You can work around this issue by disabling results buffering for the query:
 >
 > ``` php
-> $query = $articles->find()
->     ->select(['id'])
->     ->disableHydration();
->
-> foreach ($query as $row) {
->     $id = $row['id'];
->     // Process individual values
-> }
+> $results = $articles->find()
+>     ->disableBufferedResults()
+>     ->all();
 > ```
 >
-> **Option 2: Select only the fields you need**:
+> Depending on your use case, you may also consider using disabling hydration:
 >
 > ``` php
-> $query = $articles->find()
->     ->select(['id', 'title'])
->     ->disableHydration();
->
-> $ids = [];
-> foreach ($query as $row) {
->     $ids[] = $row['id'];
-> }
+> $results = $articles->find()
+>     ->disableHydration()
+>     ->all();
 > ```
 >
-> These approaches avoid loading unnecessary data and provide better memory
-> efficiency for large result sets.
+> The above will disable creation of entity objects and return rows as arrays instead.
 
 ### Getting the First & Last Record From a ResultSet