Bug #26862

Doctrine\Query is not serializable

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

Status:
Resolved
Priority:
Must have
Category:
Persistence
Start date:
2011-05-17
Due date:
2011-05-18
% Done:

100%

Estimated time:
PHP Version:
Has patch:
Complexity:

Description

For widgets, it is crucial that Query objects are serializable and deserializeable,
so one should be able to do:

$newQuery = deserialize(serialize($query))
$newQuery->execute() (or something else)

Maybe a functional test for this would be nice?

One thing I already discovered further is that the properties in QueryResult should be protected, not private.

Greets,
Sebastian


Related issues

Related to TYPO3.Flow - Bug #28995: Deferred Loading does not work with Doctrine QueryResultResolvedSebastian Kurfuerst2011-08-16

Actions
#1

Updated by Mr. Hudson about 10 years ago

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

#2

Updated by Karsten Dambekalns about 10 years ago

  • Status changed from Accepted to Under Review
#3

Updated by Mr. Hudson about 10 years ago

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

#4

Updated by Mr. Hudson about 10 years ago

Patch set 3 of change Ifd8ed7a46d9701c406e186e2d3b3d6b1f39596e0 has been pushed to the review server.
It is available at http://review.typo3.org/2400

#5

Updated by Karsten Dambekalns about 10 years ago

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

Also available in: Atom PDF