On Thu, 2002-06-13 at 13:14, Stephen Haberman wrote: > > 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. >
I think the method internals could be done generally. I'm not sure how easy it is to generate a suitable method name generally. The other method (getParentModules) will require using aliases which had not been added to criteria when i first coded the templates, but it has since been added. john -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
