On Thursday, February 9, 2012 1:28:28 PM UTC-5, Lewis wrote: > > Then why did web2py fail with a run time error? Or why wasn't the run > time error trapped? Maybe because I had requires on the same table > for a different constraint? >
I assume there must be an explicit "requires" attribute set for that field somewhere, so the automatic setting of "requires" isn't happening. You'll have to show more code. > It doesn't look good when visitors to your site see the web2py error > ticket page. You can generate friendly error pages -- see http://web2py.com/books/default/chapter/29/4#Routes-on-error. The error page can be a static file, or a dynamically generated page. In the latter case, it might be safer to have the error handler in a separate error handling application -- that way if the error happens to be in a model file of your main app, it won't prevent the error handler from being reached. Anthony
