It's not exactly bad practice, quite the contrary, usually you want to start with a database without redundancy. This is just a case where denormalization really yields fruits as it is very inefficient to have to query the jobs and projects table to know who is the owner of a task. An alternative, if you don't want to do this, is to cache the tasks of the user either in session or in cache disk and then you see if the task belongs to the set. You will then have to be careful and delete/update this cached version if there are new tasks for that user.
-- 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.
