Feature #32990
Account party property should be persistable through the account
| Status: | Rejected | Start date: | 2012-01-05 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Aske Ertmann | % Done: | 0% |
|
| Category: | Persistence | |||
| Target version: | - | |||
| PHP Version: | 5.3 | Complexity: | ||
| Has patch: | Yes |
Description
Before:
- @ORM\ManyToOne(inversedBy="accounts")
After: - @ORM\ManyToOne(inversedBy="accounts",cascade={"all"})
In order to make account party properties changes through a fluid form with the account as the property.
History
#1 Updated by Gerrit Code Review over 3 years ago
- Status changed from New to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/7680
#2 Updated by Karsten Dambekalns over 3 years ago
- Assigned To set to Aske Ertmann
Please, using cascade should never be needed. FLOW3 determines this from the aggregate boundaries.
In this particluar case you need to use the PartyRepository to update the party explicitly.
#3 Updated by Christian Müller over 3 years ago
- Status changed from Under Review to Rejected