> The table has a self-referential key to set up parent/child > relationships. The method getScarabModulesRelatedByParentId is a bit > ambiguous. When writing the template I was thinking a method named like > this should return results similar to a method named getParentModules. > What it will return is ChildrenModules. This is the reason for not > generating these methods. If others do not find this confusing, I am ok > with the patch.
I agree that it's not the clearest thing in the world, but I would hope users would get it after a few tests, even if they don't at first. Given that you already trap for this parent/child foreign key reference situation, could you implement getParentModules/getChildModules instead of the ambiguous getModulesRelatedByParentId? I'm not familiar enough with the template to know whether it's possible or not and could be done generally for all (most) situations. - Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
