> Possibly, it would be wiser to add a generic fetch(ForeignKey) and > fetchOne(ForeignKey) method, that allows for navigating data through foreign > keys...
Definitely. I have an N:M join table that links predecessor to successor articles. So it has two foreign keys, one to the predecessor article, one to the successor article. And it would make a huge difference which of the two FKs I'm following! In other tables, I'm having stuff like "company-specific relationships". Say, each article has an additional company field, and the predecessor-successor article would have three fiels: company pred succ The predecessor FK would consist of company&pred, the successor FK of company&succ. That's a case of overlapping FKs.
