[TYPO3-ect] Symmetric MM-Relations

[Elmar Hinz]

Sebastian Kurfuerst wrote:
> Hi Elmar,
> 
>> The relation itself is still anbalanced. It can relate one table type to
>> many table types by setting the field "tables". It is still not possible
>> to select from many table types from both sides of the relation. We
>> would need to fields "tables" to do this.
>>   
> Ingmar and me did not see the need to implement this, because we did not
> see the point in having just one relation table (it would be much harder
> to debug, for example).
> 

Hi Sebastian,

my current main concern is the CCF. I looked into SVN yesterday night.
Your solution seems to work for it. There is only one table for the
common category tree. So I can go foreward now. I will publish a first
working version within the next few weeks.

In the trees library "Better Trees" (trees) it is also possible to build
a tree as a mix of different tables, by defining parent child realations
between them. If someone likes to relate different tables to this
heterogenious tree he will come to the point, where a commom MM relation
table of the symmetric type would be the cleanest solution.

Even then he still can work with the bidirectional assymetric relations,
you have implemented. Then he needs to set up one mm table for every
table or beeing more precisely one for every type of relation, if no
attributes are available to set the type of the relation (role).

To simply hardset the type of a relation (role) a single additional
configuration would be needed like in extension "mmforeign" from Rene.

conf => array(
   ...
   MM => 'tt_address_fe_groups_mm',
   ...
   MM_type => 'teacher'
   ...
)

But with this, there still isn't the possiblity to select muliple roles
from a second list. That would indeed require a TCE field with 2
multiple selects combined and a more complex adaption of TCE insert,
update and select.

Regards

Elmar