On Monday, March 28, 2011 1:12:09 PM UTC-4, Massimo Di Pierro wrote: > > I am looking at the source code right now. Currently this does not > override the behavior of individual define_table(s). It just provides > the default behavior in case a migrate argument is not passed. Since > this is undocumented bahviour it can be changed and, the more I think > about it, the more I feel it should be changed and DAL(migrate) should > override define_table(migrate)
I suppose you could make a case for either behavior. The way it currently works, DAL(migrate) simply provides the default value for define_table(migrate) when the latter isn't specified. That makes it easy to turn off most migrations but selectively turn on migrations for just a few tables. On the other hand, the current method doesn't provide an easy way to temporarily override the explicit migration settings for all tables. I'm not sure which is more useful. Of course, we could always offer both options via some additional "override" argument. Anthony
