I'm not explicitly storing the country or state because the city has a 
reference to a state which has a reference to the country.

I don't think I'm breaking MVC much more than it is already routinely 
broken in web2py whenever you use SQLFORM, as the states and countries on 
the dropdown have their controller functions and LOCATIONS_SELECT doesn't 
break MVC any more than any of the helpers or widgets already included in 
web2py. If it burns your eyes for it to be in a model file, just put it in 
a module (you could call it custom_widgets.py or something) in the modules 
folder of your application. My point is, it is no more breaking of MVC than 
importing any widget in your model.

-- 
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to