Bug #28995

Deferred Loading does not work with Doctrine QueryResult

Added by Sebastian Kurfuerst about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Must have
Category:
Persistence
Start date:
2011-08-16
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
Complexity:

Description

When looking into Doctrine\QueryResult, it becomes obvious that the rows are not lazily initialized on first access, but initialized all the time. This is a severe performance penalty.

In #26862 the Doctrine Query was made serializable; but it was never accessed as the QueryResult was not lazy. This needs to be fixed.


Related issues

Related to TYPO3.Flow - Bug #26862: Doctrine\Query is not serializableResolvedKarsten Dambekalns2011-05-172011-05-18

Actions
Has duplicate TYPO3 Flow Base Distribution - Bug #29045: Wakeup of Query sets wrong state if originally no constraint has been setResolved2011-08-17

Actions
#1

Updated by Mr. Hudson about 10 years ago

  • Status changed from Accepted to Under Review

Patch set 1 of change Ide7faf982f68efe15eb2fdaa5c68063b7770a735 has been pushed to the review server.
It is available at http://review.typo3.org/4358

#2

Updated by Mr. Hudson about 10 years ago

Patch set 2 of change Ide7faf982f68efe15eb2fdaa5c68063b7770a735 has been pushed to the review server.
It is available at http://review.typo3.org/4358

#3

Updated by Sebastian Kurfuerst about 10 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF