On 1/26/06, Robert Wittams <[EMAIL PROTECTED]> wrote: > > I think all that is needed here is education - it needs to be pointed > out what the costs of subtyping are.
I agree. I think most of the time the join is going to be simple anyhow... take comments for instance. Say I have a Comment class and 3 different subtypes. If I just want the MusicComments, the join is a simple one between two tables (and would only scary with a deep inheritance tree) Now if I want to look at ALL the comments, the join is on 4 tables (barring select_related). The equation is simple: # of joins = # of subclasses, but only when you access a superclass. Poor java programmers ;-) > One option would be to provide a method on managers to provide a "faster > but broken" manager, ie joinless. It needs to have a name to suggest > that it is not really recommended though, and should only be used if it > actually has a beneficial performance impact... My gut reaction is to punt on this and wait to see if it has some real life use. (i.e. if the default way is intolerably slow.) It's not a huge api change to add it later. Joseph
