Feature #29037

Feature #28486: Don't clone, use explicit change tracking instead

Use annotation to mark entities as aggregate root

Added by Karsten Dambekalns about 10 years ago. Updated about 10 years ago.

Status:
Rejected
Priority:
Should have
Category:
Persistence
Start date:
2011-08-17
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
Complexity:

Description

  • @aggregateRoot annotation (normative)
  • Repository CAN exist for non-aggregate root -> EXPLAIN that this is pragmatic, but no clean DDD

Related issues

Blocks TYPO3.Flow - Feature #29038: Set useful defaults for cascade attributes in DoctrineResolvedKarsten Dambekalns2011-08-17

Actions
#1

Updated by Mr. Hudson about 10 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 about 10 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 about 10 years ago

  • % Done changed from 0 to 100

Also available in: Atom PDF