[TYPO3-project-formidable] RFC: m:n relations

[Jerome Schneider]

Hi Oliver,

Thanks for this nice work, I tried and it worked great, even with 
multiple values and when removing relation :)


Some questions:


* It's made to work only with "selector-like" renderlets, like listbox 
or checkbox, right ?


* _extractMmRelationsFromFormData(&$formData) seems to modify the value 
of the processed mm field in formData ; is it needed to do so ? If i'm 
asking this it's because if the original value of the flat relation ( 
comma-separated like 1,2,3,4 ) could be kept and stored in the parent 
table for the field defining the mm-relation, all the LISTER would still 
be fully functional, and especially the search ( as long as the true 
mm-relation and it's flat notation in the parent table are synchronized, 
of course )

* would you agree these enhancements to be integrated directly into 
dh_db ? (of course with all references to you)
it would greatly simplify the process of maintenance and evolution if 
working on only one datahandler, and doing so mm-stuff could also take 
advantages of the i18n work we recently had in formidable


Best regards,
Jerome Schneider



Oliver Klee a écrit :
> Hi all,
> 
> for the Seminar Manager extension, I've written a child class of tx_dhdb
> that implements m:n relations. I'd like to get feedback and comments on
> that implementation so I can make it a patch for FORMidable.
> 
> This is how to use it in the XML:
> 
> <datahandler:DBMM>
> 	<tablename>tx_seminars_seminars</tablename>
> 	<keyname>uid</keyname>
> 	<labelname>title</labelname>
> 	<mmrelations>
> 		<relation field="place" mmtable="tx_seminars_seminars_place_mm" />
> 		<relation field="speakers" mmtable="tx_seminars_seminars_speakers_mm" />
> 	</mmrelations>
> </datahandler:DBMM>
> 
> The attached file is said child class.
> 
> Regards
> 
> 
> Oliver