On Saturday, October 31, 2015 at 8:23:50 PM UTC-4, Vinicius Assef wrote:
>
> The best scenario I see is defining methods to model classes.
>
> For example, centralising queries and business actions like:
> create_customer(), get_active_employees(), register_student() and so on.
>
If those are generic functions intended to operate on different tables with
common fields, they can simply be implemented as functions. By if you want
methods on models themselves, you can do:
@db.employee.add_method.get_active_employees
@db.contractor.add_method.get_active_contractors
def get_active(self):
return self._db(self.is_active == True).select()
active_employees = db.employee.get_active_employees()
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.
