[TYPO3-core] IRRE implementation bugs

[Oliver Hader]

Hi guys,

sorry for posting to this thread late. I was under project pressure the
last few weeks and didn't find much time for Core topics. Thanks Ingmar
for pointing out the IRRE possibilities! :)

I've just some annotations...

Ingmar Schlecht schrieb:
> Kasper Skårhøj wrote:
>> About IRRE being purely M-1 is not logical for me. The full potential
>> is if it can handle M-M. For me many M-M situations warrants that I
>> can edit the children directly in the parent form, even if they are
>> children of other parents. That is a question of convenience.
> 
> I find it inconsistent usability-wise if IRRE children are sometimes
> copied along and sometimes not; changes in children sometimes affect
> other parent's children and sometimes not (same goes for moving,
> deleting and versioning) and at the same time found that the "treat as
> one object" approach is the one that is more often to be found and
> therfore the one to go for.
> 
> But there's something called combination view (useCombination=1) in IRRE
> which makes it possible to actually edit MM relations. The trick is that
> the 1:n IRRE relationship actually goes to an intermediate table (the MM
> table) which has a full TCA configuration and connects the two other
> tables. If one of the fields of that intermediate table is a DB relation
> field (group or select) then IRRE offers to edit the record that
> relation field points to directly inside of the form as well, with big
> red warning labels so you know you're editing something that affects
> other places as well.

In general IRRE handles 1:n relationships. The mentioned
MM-relationships are different to those we knew before - so I tend to
call them m:n relationships. It works like MM but the intermediate table
has a uid and pid and allows a bidirectional view from each side.

This m:n relationship is also a combined 1:n relationship:
(see UML screenshot in attachment)
* 'hotel' -> intermediate table 'hotel_offer_rel' (=1:n)
* 'offer' -> intermediate table 'hotel_offer_rel' (=1:n)
In this case, the intermediate table is seen as the "child" table that
could be accessed from both sides of the relation - hotels and offers.

The chapters 3 and 4 of my thesis [1] (try to) describe what is possible
with IRRE and what effetcs it has (e.g. on copying, moving, etc.).


olly

[1] http://typo3.org/uploads/media/Inline_Relational_Record_Editing_01.pdf
-- 
Oliver Hader
http://inpublica.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: uml_mnasym_1.png
Type: image/png
Size: 10085 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20071025/536a88f1/attachment.png