In the current release form.accepts validates the input against a copy of the db field requires and that is OK most of the time but to cover for cases like this one it would also need to check against the db field requires, in case it was modified afterwards.
But this method implies complexity in the controller and is not intuitive: 1) create widget for input and use the requires for things like drop- down generation and input validation. 2) modify requires for db side needs, which is the true use of requires. How would you modify the OptionsWidget to separate input-requires from db-requires, and at the same time keep it intuitive?. A convention? the first validator on the list is used for drop-downs an such? is this backward compatible? Or by perfecting the clone field trick? Denes. --~--~---------~--~----~------------~-------~--~----~ 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 web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
