Tickets :: Comment on [#10880] Rdo: Make *- to-one-relations aware of "no relation" state

* Your Email Address
* Spam protection	Enter the letters below: .__ __ .__ . ..__ [__)/ `[__)\|\ \|[__) [__)\__.\| \| \\|\| \
Comment	> It seems like lazy [one\|many]_to_one relations are resolved by a > different part of code than eager relations. > > lazy relations: > Base.php __get triggers a findOne on the target mapper with either a > supplied query object (undocumented?) or the defined foreignKey > field's value. A findOne without restrictions catches the first > object, if any exist or null otherwise. I think I have fixed THIS > > eager relations: > REFERENCING Objects with broken eager relations of either type (null > value or wrong key value) simply aren't created. No exception is > thrown until code wants to access the object's properties. > This seems to be handled by Horde_Rdo_Query generating an INNER JOIN > which results in no object > No idea how to tackle this.
Attachment
Watch this ticket