Feature #6140

ClassSchema must reset identity property and identifier property when being made value object

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

Status:
Resolved
Priority:
Should have
Assignee:
Karsten Dambekalns
Category:
Reflection
Target version:
TYPO3 Flow Base Distribution - 1.0 alpha 8
Start date:
2010-01-21
Due date:
% Done:

100%

PHP Version:
Has patch:
Complexity:

Description

If a class schema exists, and the type is set to value object, properties only useful for entities must be reset.

Related issues

Related to TYPO3.Flow - Feature #6142: Class schema must check for entity when setting identity and identifier property Resolved 2010-01-21

Associated revisions

Revision a141272f (diff)
Added by Karsten Dambekalns almost 10 years ago

[+FEATURE] FLOW3 (Property): The PropertyMapper now only maps to settable properties and no longer relies on the class schema to determine the type for the target property - it uses the setter parameter's type if available and falls back to the class schema if needed. Resolves #5612.
[+FEATURE] FLOW3 (Reflection): When reflecting classes entities and value objects are checked for being declared prototype, resolves #6141.
[+FEATURE] FLOW3 (Reflection): ClassSchema now enforces consistency when it comes to value objects and identity/identifier properties, resolves #6140, resolves #6142.
[+BUGFIX] FLOW3 (Persistence): Fixed left over JCR constant in AbstractSqlBackend, fixes #6153.

History

#1 Updated by Karsten Dambekalns almost 10 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r3746.

Also available in: Atom PDF