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

Oliver Klee typo3-german-02 at oliverklee.de
Tue May 29 17:57:48 CEST 2007


Hi Jerome,

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

That's correct.

> * _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 )

Yes, that's necessary - at least if we want the data to be compatible to
the way TYPO3 uses m:n relations in the BE. (It stores the number of
related records in the field - some kind of caching, I suppose.)

The other way round, I suppose the lister and the search function still
need to be adapted to m:n relations (I haven't used them yet and so
haven't thought of adapting them yet).

> * 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

That's what I was thinking of. Integrating it would be great. :-)

Regards,


Oliver


More information about the TYPO3-project-formidable mailing list