I do not understand the Italian words in your posts, but I think I am facing the same problem. My problem is narrowed down to standardization tables. In most cases I implement the first solution, that is when the content of standardization tables is not displayed in the view and only bears relevance in queries. However, in my address table and service table I use the second solution, to link a city to a standardization table with city names and to link services to a standardization table with service names.
The second solution makes displaying addresses and services a lot easier, and, I guess, enables me to implement the city and service fields as auto-complete fields (a problem I have not solved yet), not as drop boxes. However, the downside is that when I update a city or service in their respective standardization tables the update is not cascaded. onupdate='CASCADE' is not supported in web2py, I added the ON UPDATE CASCADE behavior in the database, hoping this would not interfere with web2py. So far, I did not run into any problems, but I still have my doubts when it comes to the beauty of the second solution. Annet. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
