On Wed, Jul 23, 2014 at 1:20 PM, Anthony <abasta...@gmail.com> wrote:
> I think you're right -- those attributes shouldn't trigger the lazy > definition. on_define would be more useful in case something expensive is > happening in defining one of the attributes. Also, if you define an > IS_IN_DB or IS_NOT_IN_DB that has a Set object as the first argument (as > the query will involve doing something like db.sometable.somefield == > some_value, which would cause sometable to be defined). thanks, I will amend my PR.. -- *Tim Richardson, Director* GrowthPath, Data-driven profit growth Mobile: +61 423 091 732 Office: +61 3 8678 1850 I tweet useful business & IT tips at growthpath_au GrowthPath Pty Ltd ABN 76 133 733 963 <http://www.growthpath.com.au/> -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
