Feature #28137

Do not use clone in PersistentObject ParamConverter

Added by Benjamin Eberlei about 4 years ago. Updated almost 4 years ago.

Status:Closed Start date:2011-07-13
Priority:Should have Due date:2011-07-13
Assigned To:Karsten Dambekalns % Done:

100%
Category:Persistence
Target version:TYPO3 Flow Base Distribution - 1.0 beta 1
PHP Version: Complexity:
Has patch:

Description

Currently clone is used inside the PersistentObject ParamConverter and objects have to be merged back into persistence context (in case of doctrine) using $em->merge(). This creates unnecessary performance problems where the state of an object is first moved into a new object, then moved back into the persistent object.

This is a dependency of the previous transaction ticket, since cloning is currently necessary with transactions always being flushed to the database.

Related issues

duplicates TYPO3.Flow - Task #29039: Change default policy for Doctrine to DEFERRED_EXPLICIT Resolved 2011-08-17
follows TYPO3.Flow - Feature #28136: HTTP Semantics for Transactions and more New 2011-07-12

History

#1 Updated by Karsten Dambekalns almost 4 years ago

  • Project changed from TYPO3 Flow Base Distribution to TYPO3.Flow

#2 Updated by Karsten Dambekalns almost 4 years ago

  • Category set to Persistence
  • Status changed from New to Closed
  • Assigned To set to Karsten Dambekalns
  • Target version set to 1.0 beta 1
  • % Done changed from 0 to 100

Resolved by duplicate issue #29039.

Also available in: Atom PDF