Open richjoslin opened 12 years ago
Remember that you'll only see an on screen error if you are working local or have them turned on.
That's good to note. If we are able to catch the error and display the error message to the screen, that'll be a slight speed boost during dev - just need to make sure it redirects to friendly 500 on the live site, like you said. I haven't tested that lately. Custom error pages would be some pretty easy unit tests to set up, too.
I'm thinking we can override the select/insert/update/delete routines to use a try catch so that DATABASE ERROR doesn't get dumped to the screen instead of either a detailed error message or a friendly 500 error page.