But they are not. I can't understand why as the fact that they are referenced seems to be the only thing that trigger them to be defined at each request. I mean if I comment the reference field they stop to be defined they goes in the lazy array in response.toolbar db.tables...
So, I don't think that it comes from a table call somewhere else in the app (I have check for that as much as I can anyway). Any idea? I think I will try trunk to see if it fixed... Hope trunk is stable enough... Richard On Tue, Mar 14, 2017 at 11:35 AM, Leonel Câmara <[email protected]> wrote: > Referenced tables should be lazy yes as long as you use the string version > "reference anothertable". > > -- > Resources: > - http://web2py.com > - http://web2py.com/book (Documentation) > - http://github.com/web2py/web2py (Source code) > - https://code.google.com/p/web2py/issues/list (Report Issues) > --- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
