Feature #29037
Feature #28486: Don't clone, use explicit change tracking instead
Use annotation to mark entities as aggregate root
Status: | Rejected | 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
- @aggregateRoot annotation (normative)
- Repository CAN exist for non-aggregate root -> EXPLAIN that this is pragmatic, but no clean DDD
Related issues
History
#1 Updated by Mr. Hudson almost 4 years ago
- Status changed from Accepted to Under Review
Patch set 1 of change I91089649a4f30990e17645110febebc36263236b has been pushed to the review server.
It is available at http://review.typo3.org/4468
#2 Updated by Karsten Dambekalns almost 4 years ago
- Status changed from Under Review to Rejected
We decided to leave the behavior as it was, if a repository exists for an entity, it is considered aggregate root.
#3 Updated by Karsten Dambekalns almost 4 years ago
- % Done changed from 0 to 100