Bug #55954
Task #55953: Repair and streamline ValueObject support
Associations to ValueObjects should not be cascade all'd
Status: | New | Start date: | 2014-02-13 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | - | |||
Target version: | - | |||
PHP Version: | Complexity: | |||
Has patch: | No | Affected Flow version: | (any) |
Description
As it's the case for associations to entities being an aggregate root, Associations to ValueObjects must not be delete-cascaded carelessly because they are likely to and may be associated to other entities.
This means, as far as I understand it, occurrences like
Packages\Framework\TYPO3.Flow\Classes\TYPO3\Flow\Persistence\Doctrine\Mapping\Driver\FlowAnnotationDriver.php:5071elseif ($this->isAggregateRoot($mapping['targetEntity'], $className) === FALSE) { 2 $mapping['cascade'] = array('all'); 3}
etc.
must also check for the target entity being a ValueObject.
History
#1 Updated by Bastian Waidelich 6 months ago
Just a little reminder (for all major candidates for Flow 3.0): Feature Freeze is in 10 days! Let me know if you need any help with this.