Feature #32990

Account party property should be persistable through the account

Added by Aske Ertmann almost 10 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
Category:
Persistence
Target version:
-
Start date:
2012-01-05
Due date:
% Done:

0%

Estimated time:
PHP Version:
5.3
Has patch:
Yes
Complexity:

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.

#1

Updated by Gerrit Code Review almost 10 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 almost 10 years ago

  • Assignee 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 almost 10 years ago

  • Status changed from Under Review to Rejected

Also available in: Atom PDF