put you table definitions on modules and use conditional models to instantiate them.
http://zerp.ly/rochacbruno Em 15/05/2012 05:44, "Annet" <[email protected]> escreveu: > > Right now you can't have one model apply to two different controllers with >> conditional models. Copy/pasting should work but I would rarely advise >> that. Are you running into performance problems? > > > No, but I read the posts in the group, and thought I'd better prevent > running into performance problems. > > >> Have you tried any other optimizations? 48 tables is kind of a lot but >> not crazy. > > > It's a network application based on nodes > (people,organizations,resources) hubs and edges (that's 6) with address > book functionality based on apple's address book (that's 9), calendar > functionality (6), auth and account functionality (that's 10), view > settings (that's 6), and standardization tables (that's 11). > > I try to keep the number of tables as limited as possible, I also > considered developing a separate address book, calendar and cms application > but in that case I have to define the same constants, variables etc. more > than once, which may result in inconsistencies. > > Since the address book and calendar are queried based on keyword/locality > c.q. startDate/endDate the result sets don't contain more than a 100 > records max. > > As I acquire more knowledge on this subject I might consider other > solutions. > > > Kind regards, > > Annet. >
