Feature #37372
Inheritance in ORM should be configured automatically
| Status: | Accepted | Start date: | 2012-05-21 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Karsten Dambekalns | % Done: | 0% |
|
| Category: | Persistence | |||
| Target version: | TYPO3 Flow Base Distribution - 2.1 | |||
| PHP Version: | Complexity: | |||
| Has patch: | No | |||
| Votes: | 3 (View) |
Description
When classes are extended, inheritance should be configured automatically for Doctrine, using sane defaults. This avoids the need to foresee future needs when coding - especially for packages that are of general purpose and where no one can know in the beginning whether they will be extended or not.
Related issues
| related to TYPO3.Flow - Feature #37373: Make annotation overrides / "injection" via Objects.yaml ... | Under Review | 2012-05-21 | ||
| related to TYPO3.Flow - Feature #41297: Add a way to extends the Account security model | Under Review | 2012-09-23 | ||
| related to TYPO3.Flow - Task #27283: Handle @InheritanceType in a correct manner | Resolved | 2011-06-07 | ||
| blocks TYPO3.Media - Feature #47262: Easily extending the Image Model | Accepted | 2013-04-15 |
History
Updated by Karsten Dambekalns 5 months ago
- Target version changed from 2.0 beta 1 to 2.1