If you need code that is only executed for a specific controller, why not put it directly in the controller?
Massimo On Jun 11, 9:19 am, AchipA <attila.cs...@gmail.com> wrote: > I could say the same for views (why are we bothering to define views > by filename/convention then ?). Littering the models with if-s won't > make them pretty, newbie friendly nor as quick as they could be. > > On Jun 11, 3:28 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > You can add "if" statememts in models > > > On Jun 11, 8:03 am, AchipA <attila.cs...@gmail.com> wrote: > > > > I was wondering of a possibility of speeding up models (especially if > > > you have several different datasources), while keeping backward > > > compatibility and also a convention over configuration approach. We do > > > everything as before, however, if there IS a model with the same base > > > name as a controller, upon the invocation of the controller we only > > > execute THAT model (it can import others with a small check to avoid > > > recursion). This would be not unlike what we do with views now (check > > > for a default naming convention, fall back to generic if that fails). > > > Thoughts, comments ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
