[TYPO3-mvc] Attributes on irre-relations possible?

[Andreas Kießling]

Hi Steffen,

> I talked about IRRE Handling with Jochen last week.
> There's a difference between what the "tutorial" and the "core-api"
> tells IRRE Users.
> Jochen went along the tutorials building the IRRE. But this prooved as
> complicated since there's no real "prediction" possible what the child
> record will be (same configuration, different result).
> The current CORE API is a bit more precise there and does not allow
> "dirty configuration" but also enables "typical mm support".
> Since the core-api version technically is more precise, and tutorials
> some kind of outdated, we came to the conclusion that in 4.3.x we will
> stick to the current behavoiur and try to fix as much as possible and
> with 4.4 (and so extbase 1.2) introduce the new behavoiur along api.
>

I'm afraid to hear about these problems related to IRRE. I always refer 
to the examples from irre_tutorial and the wiki-pages, if an extension 
with these features is needed. Maybe you or Jochen could point out, what 
"dirty configurations" should be avoided? CSV is obvious, but also mm 
relations are not the preferred way, according to the documentation 
(according to changelog of irre_tutorial from last TER-update). If 
you're new to IRRE, it's likely you stick to "the old style" and use 
what has worked before if it is not stated clearly to avoid that.

> So in short:
> this won't be possible in extbase <= 1.1.x (4.3.x)
> for extbase 1.2.0 (>= 4.4.0) IRRE handling will be refactored, then
> foreign_selector will do its jobs in extbase correctly.
>
> You may use "1.2" patches (afaik currently not public). I may provide
> mine, which work for now, but for shure they won't be the exact 1.2
> implementation.

Since i only need that feature for an internal extension / my extbase 
playground, SVN and patched versions are not a problem. I'd be glad to 
test your patches!

Greets and thank you for your detailed answer,
Andreas