[TYPO3-irre] Converting old mm-tables to IRRE

Mischa Heißmann typo3 at heissmann.org
Tue Apr 24 11:11:35 CEST 2007


Hi Oliver,

thanks for the hint. I will try it asap. The problem is, that our 
customer made the new specification of bidirectional allocation of 
datasets. Since now, the allocation was done by an mm-table which is 
only for one way.
Creating a complete new extension will be followed by a complete 
convertion of old data and recoding of the extension. So I try to change 
the extension, using the old mm-table.

Mischa

Oliver Hader schrieb:
> Hi Mischa,
> 
> Mischa Heißmann wrote:
>> I try to use old mm-tables with uid_foreign and uid_local as a base for
>> an IRRE featured extension.
>> Will say: I've got an old ext with mm-tables and like to convert it
>> easily into an IRRE.
>>
>> Has anybody experiences or can somebody help me what to do? Using the
>> tutorial doesn't help very much.
> 
> You can do this by e.g. the following in your TCA columns section:
> 
> ...
> 'children' => array(
> 	'label' => '...',
> 	'config' => array(
> 		'type' => 'inline',
> 		'foreign_table' => 'tx_myext_child',
> 		'MM' => 'tx_myext_parent_child_mm',
> 		'appearance' => array(...),
> 	)
> )
> ...
> 
> But the question is, what are you planning to do. The intermediate table
> used for real MM relations doesn't have a uid. This means that a
> relation is not identified unique by one parameter - but by three
> (uid_local, uid_foreign, tablenames) which have to be pushed to every
> point where two entities shall get related to each other by MM.
> This is the reason why regular MM relations are not fully supported and
> implemented in IRRE. Maybe this gets improved for TYPO3 4.2 if there is
> a general request to have it inside the Core.
> 
> But as mentioned, the disposal of IRRE with 1:n/m:n or the old TCA types
> using MM depends on your specific demands and scenario.
> 
> 
> olly


More information about the TYPO3-project-irre mailing list