[PR #955] [MERGED] iteration risk note #8956

New Issue

admin · 2026-01-22T16:02:29+01:00

admin commented

2026-01-22 16:02:29 +01:00

📋 Pull Request Information

Original PR: https://github.com/doctrine/orm/pull/955
Author: @goatherd
Created: 2/17/2014
Status: ✅ Merged
Merged: 3/23/2014
Merged by: @beberlei

Base: master ← Head: patch-1

📝 Commits (1)

0677423 iteration risk note

📊 Changes

1 file changed (+6 additions, -0 deletions)

View changed files

📝 docs/en/reference/batch-processing.rst (+6 -0)

📄 Description

instead of loading the whole result into memory at once

is not the full truth.

There is a certain risk of processes getting killed due to memory allocation with large iteration. This is caused by result buffering of the client. It is not always being visible to PHP as http://www.php.net/manual/en/mysqlinfo.concepts.buffering.php suggests.

This is only a proposal for discussion as I am not certain how to best add the information or if to add it at all (was it obvious before?). Is buffered iteration even a good suggestion for anything but small sets?

On a side-note: is there a way to run unbuffered queries with Doctrine?

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/doctrine/orm/pull/955 **Author:** [@goatherd](https://github.com/goatherd) **Created:** 2/17/2014 **Status:** ✅ Merged **Merged:** 3/23/2014 **Merged by:** [@beberlei](https://github.com/beberlei) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`0677423`](https://github.com/doctrine/orm/commit/0677423d1484f81b475eac241f92a73cb7f05d4d) iteration risk note ### 📊 Changes **1 file changed** (+6 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/en/reference/batch-processing.rst` (+6 -0) </details> ### 📄 Description > instead of loading the whole result into memory at once is not the full truth. There is a certain risk of processes getting killed due to memory allocation with large iteration. This is caused by result buffering of the client. It is not always being visible to PHP as http://www.php.net/manual/en/mysqlinfo.concepts.buffering.php suggests. This is only a proposal for discussion as I am not certain how to best add the information or if to add it at all (was it obvious before?). Is buffered iteration even a good suggestion for anything but small sets? On a side-note: is there a way to run unbuffered queries with Doctrine? --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

admin added the pull-request label 2026-01-22 16:02:29 +01:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: doctrine/archived-orm#8956