[TYPO3-core] RFC: Bug: IRRE - Related child records are not updated when copying to a different page

[Martin Kutschker]

Oliver Hader schrieb:
> Hi Ingo,
> 
> Ingo Renner wrote:
> 
>>Am 15.02.2007 um 19:47 schrieb Oliver Hader:
>>
>>Hi Olly,
>>
>>
>>>Problem:
>>>A structure of 1:n dependend records (parent->child->grandchild) shall
>>>be copied and pasted on a different page than the original one. The
>>>parent record will be inserted correctly on the destination page. The
>>>child records unfortunatelly not - they are duplicated on the original
>>>page.
>>
>>Is it wanted at all to have the child records copied with the parent
>>record?
>>If I compare it with categories in news I can copy a category to a
>>different page without having to copy the child categories to the same
>>page and still having the relation intact...
> 
> 
> Inline Relational Record Editing handles direct 1:n related structures.
> Thus you can call the relationship as a composition. In this context
> children cannot exist without the existence of their parent.
> The disposal of TCA defined intermediate tables is a special case on
> this issue. The items defining the m:n relationship are the children
> depending on their parent. The underlying related records are in this
> case aggregated instead of composed.
> 
> Examples:
> 1) hotel --[1:n]--> offer --[1:n] --> price
> 2) hotel --[1:n]--> hotel_offer_rel <--[1:n]-- offer
>    or in short form: hotel <--[m:n]--> offer
> 
> Result: It is wanted that also child records which depend on their real
> parent are moved, copied or deleted according to their parent record.

You mean, deleting the hotel shall delete all offer and price records of 
this hotel? Sounds good.

But:

company --[1:n]--> job --[1:n] --> person

Just because I delete the company I don't want to delete the person (which 
may get another job at another company).

Masi