"Jorge Vargas" <[EMAIL PROTECTED]> writes: > thanks for the link Joost > > I have created a ticket this time > http://trac.turbogears.org/turbogears/ticket/1133 > > can we get some ideas on how to implement this?
This was discussed a while ago and we agreed on not splitting our model due to several relationships between classes. Who is splitting models should take care of doing the whole job. I vote for documenting what needs to be done and let whoever wants to split their model do it. I have a project with -- actually -- 100 classes and I don't believe that splitting those would make my life easier (in fact, mapping some relationships would be a lot mode annoying if I had to import and qualify classes...). I dunno how people program their databases but mine is a lot normalized and has code inside it (triggers, stored procedures, functions, views, rules, etc.) to perform better and provide more useful information. There's a project where we will reach some hundreds of tables and even there I'm not seeing how splitting the model would make my life easier. -- Jorge Godoy <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
