Feature #28486
Don't clone, use explicit change tracking instead
Status: | Resolved | Start date: | 2011-08-17 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
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 the parameter converter uses "clone" to create copies of objects,
Much better would be to automatically set the change tracking to DEFERRED_EXPLICIT for all entities: http://www.doctrine-project.org/docs/orm/2.0/en/reference/change-tracking-policies.html
This would mean changes are only tracked when you explicitly call $em->persist(). You could then switch the implementation of the Doctrine Base Repository to not use ->merge, but ->persist.
This would greatly simplify the code and make it much more robust.
Subtasks
Related issues
History
#1 Updated by Robert Lemke about 4 years ago
- Assigned To set to Karsten Dambekalns
#2 Updated by Sebastian Kurfuerst almost 5 years ago
- Priority changed from Should have to Must have
- Target version set to 1.0 beta 1
Thanks Benjamin :-)
#3 Updated by Karsten Dambekalns almost 4 years ago
- Project changed from Doctrine 2 to TYPO3.Flow
- Status changed from New to Accepted
#4 Updated by Karsten Dambekalns almost 4 years ago
- Category set to Persistence
#5 Updated by Karsten Dambekalns almost 4 years ago
- Tracker changed from Bug to Feature
#6 Updated by Karsten Dambekalns almost 4 years ago
Some notes we took when discussing this: http://typo3.ietherpad.com/FLOW3Persistence
#7 Updated by Karsten Dambekalns almost 4 years ago
- Status changed from Accepted to Under Review
#8 Updated by Karsten Dambekalns almost 4 years ago
- Status changed from Under Review to Resolved