Hi Anthony, I agree with you. It would be nice to have such a on_define function, this will not only optimize the code but also makes the code more readable. I prefer the function rather than distributing in several controllers the code that forces the definition of Auth
2013/1/15 Anthony <[email protected]> > On Tuesday, January 15, 2013 9:27:55 AM UTC-5, Paolo valleri wrote: > >> I am using lazy_tables=True at DAL definition, actually I don't know how >> to enable lazy_table for auth. Does it exist? > > > Setting lazy_tables at the DAL definition affects all tables, including > the Auth tables. > > >> As I can see, auth.define_tables doesn't take any lazy_table parameter, >> moreover in my code I have a few lines of auth.settings.* which needs auth. >> > > If you have code that directly refers to an Auth table after it has been > defined lazily, then the table will be fully defined. In that case, you > could move that code to the action that actually needs it (e.g., the user() > action). Perhaps we should add an _on_define attribute to tables so it is > possible to add an on_define function after the initial lazy table > definition. > > Anthony > >> -- > > > > -- Paolo --
