Jonathan Daugherty wrote: > # Why can't we just allow the model class defined by the user to be > # used? > > That doesn't seem promote a clean separation of "table-level" > vs. "row-level" functionality. >
Argh. What is the big deal with this? I deleted a screed from my original mail about this ridiculously overpumped goal. Just look at the downsides to the magic generated class : wierdo issues with visibility, importing, naming, inheritance (quite apart from the odd current interpretation of inheritance, things like mixins are a nightmare. Georg had something about this somewhere as well).... There are just so many downsides to having a magic generated class, I really can't get excited about seperating class and instance (this is an ORM, remember) methods... Anyway, it would still be possible to stick the class level methods in a magic module, and just have the same class appear in two modules. I think this is kind of pointless ( I do not really care about seperating these methods that much), but it is possible.
