On Saturday, May 14, 2016 at 11:45:25 PM UTC-4, Alfonso Serra wrote: > > Thanks for the advise. > Yes you are right i didnt need the join, was just following the same > pattern as other queries which does need them, not this case. > > Also right with virtual fields, they are easy to use but i dont think i > should write tens lines of code within a lambda. >
There is no reason a virtual field must be based on a lambda function -- just define a function and pass it to the virtual field constructor. > My webapp is getting big and i need a way to organize the code. > You don't need classes to organize code. > I also didnt want to mix logic with table definitions. > Why not? That's how ORMs do it -- everything related to a given model lives in a single class. After all, the logic in question does pertain to the associated model. If you must have an ORM, you might try the weppy ORM (built on top of the web2py DAL), or just switch to SQLAlchemy. But first, see this web2py DAL example: https://groups.google.com/d/msg/web2py/06Y1cEOkCeI/qbL3qmsKCAAJ. Anthony -- 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.
