I wouldn't implement that solution. Well it depends on the objective, but it seems wrong to me to have 2 user tables when the user being a customer or buyer could just be a field.
You could make this field readable=False, writable=False and then have the register controller set the default differently according to the type of user registration. The stackoverflow solution to me seems that it will create problems in the future when suddenly you have users that are both or something like that. -- 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.
