LooseCoupling
LooseCoupling copied to clipboard
preDqlSelect should check relation is LooselyCoupled to it's invoker, and not assume all LooselyCoupleable objects are.
Hello .... Me again...
Thought of another bug.
Unlikely, but if someone has a schema with an object that has a loosely coupled relation, and another loosely coupleable object that is joined normally (like I say, unlikely, but people do crazy things), it's going to add the obj_type clause to the normal relation.
I think checking whether the field for the relation on the LooselyCouplable object should be a fix for this - will add it to the pull when I'm at home (unless I'm beaten to it).