I have a lot of tables. I split them up among multiple model files to help with organization. My app is highly dynamic and data are changing in all the tables constantly. If I understand it correctly, putting the tables in modules and setting track_changes(False) would mean the tables would only be created once. I haven't thought it through completely, but it would seem that that would not cause any problems. What do you think?
Obviously, if I needed to migrate tables, that would be another matter and I would have to turn track_changes(True). But I don't expect to (hope I don't have to) (try to design it so I don't have to!) do that often. ;-) On Mar 8, 11:01 am, Bruno Rocha <[email protected]> wrote: > On Wed, Mar 7, 2012 at 11:20 PM, weheh <[email protected]> wrote: > > should one be inclined to leave db table > > definitions in models, or move those to modules as well? > > it depends on how much tables do you have in models. > > It is only done to avoid all the tables to be defined even when they are > not needed, if your app uses the tables everywhere or if you have few > tables, so it will be better to have it in models. > > -- > > Bruno Rocha > [http://rochacbruno.com.br]
