.gitignore CHANGELOG Rakefile app/controllers/application.rb config/boot.rb config/database.yml config/environment.rb config/environments/development.rb config/environments/production.rb config/environments/test.rb config/routes.rb init.rb lib/save_or_raise.rb script/about script/console script/destroy script/generate script/performance/benchmarker script/performance/profiler script/performance/request script/plugin script/process/inspector script/process/reaper script/process/spawner script/runner script/server test/test_helper.rb test/unit/save_or_raise_test.rb @@ -22,8 +22,9 @@ ... end - Sometimes the control flow (often in or called by a controller) - cannot handle an unsuccessful save. There are a few ways to handle it: + Sometimes the control flow - often in or called by a controller - + cannot handle an unsuccessful save gracefully. The programmer's + choices are: 1. Do not branch on the save() call and ignore failures. 2. Throw an exception: @@ -35,7 +36,8 @@ The exception thrown by 2 and 3 will generate a 500 HTTP code for the user in production but it will also notify an admin by email when used in combination with a plugin like exception_notification. The alternative situation generated - by 1 is possible data corruption and invalid application state. + by 1 is possible data corruption and invalid application state. Doing 1 is just + not a good idea. == The problem with save! README 9f9de536b07e5cd68c8115e9bb9cbf1253bac9b4 Ryan Lowe ryanlowe@gmail.com http://github.com/ryanlowe/save_or_raise/commit/2842215ca54d6b23fb4b15243bbda29eae499d52 2842215ca54d6b23fb4b15243bbda29eae499d52 2008-05-24T23:10:22-07:00 2008-05-24T23:10:22-07:00 add the needed parts of the Rails framework to run tests 08ae50a420481dc91e4e7f5133c92a4fbdb63a12 Ryan Lowe ryanlowe@gmail.com