You must be very careful about multiple copies of table definitions. Only one copy can be allowed to migrate the table.
Upgrading the tables in a production environment is tedious. First you must upgrade the models independent of the controllers, then use the admin app to ensure all the migrations take place, then upgrade the controllers. Very error prone. I think Bruno has the right answer. On Tuesday, May 15, 2012 2:24:43 AM UTC-4, Annet wrote: > > I read some post about models influencing performance. At the moment I > have all table definitions (48) in one file: 10_tables_db.py > > I'd like to make them conditional, however, most tables are used in two > controllers, is it possible to put table definitions in: > > models/calendar/cmscalendar/10_table_db.py > > calendar and cmscalendar being controllers. Can I simply copy and paste > the existing 10_tables_db.py file to models/calendar/cmscalendar and remove > the tables not related to the calendar? Or do I have to generate the tables > again? > > > Kind regards, > > Annet > On Tuesday, May 15, 2012 2:24:43 AM UTC-4, Annet wrote: > > I read some post about models influencing performance. At the moment I > have all table definitions (48) in one file: 10_tables_db.py > > I'd like to make them conditional, however, most tables are used in two > controllers, is it possible to put table definitions in: > > models/calendar/cmscalendar/10_table_db.py > > calendar and cmscalendar being controllers. Can I simply copy and paste > the existing 10_tables_db.py file to models/calendar/cmscalendar and remove > the tables not related to the calendar? Or do I have to generate the tables > again? > > > Kind regards, > > Annet >
